Installation documentation references files that don't exist in installer package

[MatthewFletcher]

Describe the problem

The installation instructions in the documentation reference file names and bundle options that don't match the actual files included in the trident-installer-26.02.1 package downloaded from the Releases.

1. Step 2 - CRD Creation: Instructions say to use deploy/crds/<VERSION>.yaml, but the actual directory contains specific CRD files like:

   • trident.netapp.io_tridentorchestrators_crd.yaml
   • trident.netapp.io_tridentorchestrators_crd_post1.16.yaml
   • No generic <VERSION>.yaml file exists

2. Step 4 - Operator Deployment: Instructions reference two separate bundle files:

   • bundle_pre_1_25.yaml (for Kubernetes 1.24)
   • bundle_post_1_25.yaml (for Kubernetes 1.25+)

   However, the actual installer package contains only a single bundle.yaml file.

Expected behavior

The installation documentation should either:

• Reference the actual file names present in the installer package, or
• Clarify which specific files should be used based on the Kubernetes version

Describe the solution you'd like

Update the installation documentation to match the actual file structure in the trident-installer-26.02.1 release, or include a note explaining how to map the documented steps to the actual files provided.

Additional context

Downloaded: trident-installer-26.02.1.tar.gz from v26.02.1 Releases