Updated the notebook manifests with 2024b image reference

[dibryant]

Fixes for https://issues.redhat.com/browse/RHOAIENG-12629

Updated the notebook manifests with 2024b and 2024a image references

[openshift-ci]

@dibryant: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/images	db8ea3a	link	true	/test images

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[atheo89]

Hi Diamond, I have two comments:

• Please review and incorporate the changes from the upstream PR: Updated the notebook manifests with 2024b image reference opendatahub-io/notebooks#721.

• We'll need to adjust all the tag versions by shifting them down and introducing the new version, 24b, as N. This change will need to be reflected across all the related files (ImageStreams, check-params-env.sh, params., commits., kustomization.yml). Please take extra care during this process, as it's easy to accidentally cause misalignments.

  • N - 2024.2
  • N-1 - 2024.1
  • N-2 - 2023.2
  • N-3 - 2023.1
  • N-4 - 1.2

[harshad16]

/lgtm
/approve

There are some bits, which needs to be adjust, they would followed up in next set of PR's.
Example:

• verifying the annotation

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: harshad16

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [harshad16]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[harshad16]

Merging to move along the process.

[jstourac]

these aren't correct, similar to other occurrences - though, the CI failed so it's clear and should be fixed in the followup then