[TEST] Develop a script to generate Longhorn YAML with version replacement

[roger-ryao]

What's the test to develop? Please describe

We need to automate the process of generating and customizing Longhorn YAML configuration files based on specific Longhorn versions. The goal is to download the Longhorn YAML for a given version, replace the image tags for various components with new versions (e.g., longhorn-ui, longhorn-manager, longhorn-engine, etc.), and then save the updated YAML file with a dynamically generated filename based on the version number (e.g., longhorn-v1.7.x-head.yaml, longhorn-v1.8.0-dev-20240922.yaml).

Describe the tasks for the test

• A script is provided that can:
  1. Take arguments for the old version, new version, and Longhorn version.
  2. Download the corresponding longhorn.yaml file.
  3. Perform a search-and-replace operation to update all relevant image tags.
  4. Save the final file with a filename based on the major version number.

> ./update_LH_ver_with_download.sh 

Usage: ./update_LH_ver_with_download.sh <old_version> <new_version> <longhorn_version>

Arguments:
  <old_version>       The version of Longhorn images to be replaced (e.g., v1.6.3, v1.7.1).
  <new_version>       The new version of Longhorn images to use (e.g., v1.6.3-dev-20240922, v1.7.x-head).
  <longhorn_version>  The branch or tag from which to download the Longhorn YAML file.

  Examples:

    # For downloading longhorn.yaml from the v1.6.x branch
    ./update_LH_ver_with_download.sh v1.6.3 v1.6.3-dev-20240922 v1.6.x

    # For downloading longhorn.yaml from the v1.7.x branch
    ./update_LH_ver_with_download.sh v1.7.1 v1.7.x-head v1.7.x

    # For downloading longhorn.yaml from the master branch
    ./update_LH_ver_with_download.sh master-head v1.8.0-dev-20240922 master

Additional context

N/A

[longhorn-io-github-bot]

Pre Ready-For-Testing Checklist

• [ ] Where is the reproduce steps/test steps documented? The reproduce steps/test steps are at:

• [ ] Is there a workaround for the issue? If so, where is it documented? The workaround is at:

• [ ] Does the PR include the explanation for the fix or the feature?

• [ ] Does the PR include deployment change (YAML/Chart)? If so, where are the PRs for both YAML file and Chart? The PR for the YAML change is at: The PR for the chart change is at:

• [ ] Have the backend code been merged (Manager, Engine, Instance Manager, BackupStore etc) (including backport-needed/*)? The PR is at

• [ ] Which areas/issues this PR might have potential impacts on? Area Issues

• [ ] If labeled: require/LEP Has the Longhorn Enhancement Proposal PR submitted? The LEP PR is at

• [ ] If labeled: area/ui Has the UI issue filed or ready to be merged (including backport-needed/*)? The UI issue/PR is at

• [ ] If labeled: require/doc Has the necessary document PR submitted or merged (including backport-needed/*)? The documentation issue/PR is at

• [ ] If labeled: require/automation-e2e Has the end-to-end test plan been merged? Have QAs agreed on the automation test case? If only test case skeleton w/o implementation, have you created an implementation issue (including backport-needed/*) The automation skeleton PR is at The automation test case PR is at The issue of automation test case implementation is at (please create by the template)

• [ ] If labeled: require/automation-engine Has the engine integration test been merged (including backport-needed/*)? The engine automation PR is at

• [ ] If labeled: require/manual-test-plan Has the manual test plan been documented? The updated manual test plan is at

• [ ] If the fix introduces the code for backward compatibility Has a separate issue been filed with the label release/obsolete-compatibility? The compatibility issue is filed at