Add step to update the torc with correct version

[crossond]

Page URL

https://docs.netapp.com/us-en/trident/trident-managing-k8s/upgrade-operator.html#upgrade-a-manual-installation

Page title

Upgrade a Trident operator installation

Summary

https://docs.netapp.com/us-en/trident/trident-managing-k8s/upgrade-operator.html#upgrade-a-manual-installation

For Upgrading an Offline Environment, (requiring a private registry),
ref: Support case 2009911268
JIRA https://jira.ngage.netapp.com/browse/CDS-7675

After performing the steps in the trident operator upgrade in the doc page;
The torc was still showing the old version (22.07.0), and none of the trident controller or worker pods were being re-created by the daemonset. The upgrade was stuck, Trident was not working.

We needed to add these 2 steps to complete the Offline upgrade :

Update the 'operator.yaml', 'tridentorchestrator_cr.yaml', and 'post_1_25_bundle.yaml' with the correct registry and image
paths for 23.07.1, and the correct secret.

Edit the 'torc' with the correct version being upgraded to (ie. 23.07.1 for this customer)
After editing the torc with the correct version (23.07.1) the upgrade completed. This step was provided by engineering.

............

FYI - Here is summary of the steps required to complete the upgrade for the Offline mode (private registry environment):

1. Customer pushed images to their private registry

2. Followed Manual Offline steps documented here:
   https://docs.netapp.com/us-en/trident-2307/trident-get-started/kubernetes-deploy-operator-mirror.html#critical-information-about-astra-trident-23-07

3. Updated the 'operator.yaml', 'tridentorchestrator_cr.yaml', and 'post_1_25_bundle.yaml' with the correct registry and image
   paths for 23.07.1, and the correct secret.

4. Deleted the bundle.yaml for 22.07.0 (as per the doc page)

5. Created the bundle.yaml for 23.07.1 (as per the doc page)

   At this point, the new trident-operator pod was created, but none of the other pods were re-started / created new.
   The upgrade was stuck. (The torc describe was still showing 22.07.0.)

6. Edited the trident torc to show the image 23.07.1.
   This step allowed the trident daemonset to restart all the trident node pods with 23.07.1.
   - tridentctl version -n trident showed version 23.07.1
   The trident-controller pod and all worker pods were Running, and the backend was online,

Public issues must not contain sensitive information

• This issue contains no sensitive information.