Change the update release pipeline for cflinuxfs5

[Milena-Encheva]

WHAT is this change about?

This change introduces the cflinuxfs5 release into the cf-deployment pipeline. It updates the inputs.yml file to include the cflinuxfs5 release and modifies the update-releases.yml pipeline to add jobs for acquiring and updating the cflinuxfs5 release.

What customer problem is being addressed? Use customer persona to define the problem e.g. Alana is unable to...

Alana, a platform operator, needs to ensure that the latest Linux stack (cflinuxfs5) is integrated into the deployment pipeline to support modern application requirements and security updates. This change enables the pipeline to manage and update the cflinuxfs5 release seamlessly.

Please provide any contextual information.

Part of #1323.

Has a cf-deployment including this change passed cf-acceptance-tests?

• YES
• NO

The cflinuxfs5 release is newly added and requires further testing.

Does this PR introduce a breaking change? Please take a moment to read through the examples before answering the question.

• YES - please choose the category from below. Feel free to provide additional details.
• NO

Types of breaking changes:

1. causes app or operator downtime
2. increases VM footprint of cf-deployment - e.g. new jobs, new add ons, increases # of instances etc.
3. modifies, deletes or moves the name of a job or instance group in the main manifest
4. modifies the name or deletes a property of a job or instance group in the main manifest
5. changes the name of credentials in the main manifest
6. requires out-of-band manual intervention on the part of the operator
7. modifies the ops-file path, changes the type, changes the values or removes ops-files from the following folders
   • ./operations/ or ./operations/experimental
   • ./addons
   • ./backup-and-restore/

If you're promoting an experimental Ops-file (or removing one), Please follow the Ops-file workflows.

Ops files changes in the following folders are considered as NON BREAKING CHANGES
./community, ./example-vars-files, ./test

How should this change be described in cf-deployment release notes?

Added support for the cflinuxfs5 release in the cf-deployment pipeline. This includes pipeline jobs for acquiring and updating the release.

Does this PR introduce a new BOSH release into the base cf-deployment.yml manifest or any ops-files?

• YES - cflinuxfs5
• NO

Does this PR make a change to an experimental or GA'd feature/component?

• experimental feature/component
• GA'd feature/component

Please provide Acceptance Criteria for this change?

Verify that the cflinuxfs5 release is listed in the inputs.yml file:

grep "cflinuxfs5" ci/input/inputs.yml

Verify that the update-cflinuxfs5 job is present in the update-releases.yml pipeline:

grep "update-cflinuxfs5" ci/pipelines/update-releases.yml

Run the pipeline and ensure the update-cflinuxfs5 job completes successfully.

What is the level of urgency for publishing this change?

• Urgent - unblocks current or future work
• Slightly Less than Urgent

Tag your pair, your PM, and/or team!

@oliver-heinrich @jochenehret