Jupyter tile, merge cert info from old notebook to avoid loss

[andrewballantyne]

https://issues.redhat.com/browse/RHOAIENG-6455

Description

Merges in the volumeMounts, and the notebook container's volumes & envs to keep the cert information around instead of overriding it with the k8s patch logic.

How Has This Been Tested?

Manually using the Jupyter tile.

Needs self signed cert stuff setup (cc @harshad16 for details)

1. Go to the Jupyter tile
2. Create a notebook - details do not matter (if you have one before this, delete it & the PVC)
3. Check the yaml on OpenShift Console (look for the ca-bundle references)
4. Stop Notebook
5. Create the notebook again
6. Check the yaml still has the ca-bundle references

Test Impact

None, backend only change.

Request review criteria:

Self checklist (all need to be checked):

• The developer has manually tested the changes and verified that the changes work
• Commits have been squashed into descriptive, self-contained units of work (e.g. 'WIP' and 'Implements feedback' style messages have been removed)
• Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
• The developer has added tests or explained why testing cannot be added (unit or cypress tests for related changes)

If you have UI changes:

• Included any necessary screenshots or gifs if it was a UI change.
• Included tags to the UX team if it was a UI/UX change (find relevant UX in the SMEs section).

After the PR is posted & before it merges:

• The developer has tested their solution on a cluster by using the image produced by the PR to main

/cc @harshad16

[andrewballantyne]

@harshad16 please give it a test and let me know if this is what you're looking for.

[harshad16]

Tested this in our dev cluster.
the solution sticks to the Notebook CR changes as expected.

[harshad16]

/lgtm

thanks for the quick solution.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

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

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