Create new image v1.9.1 from upstream main

[nouranhamdy1998]

Checklist:

• Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this is a chore.
• The title of the PR is (a) conventional with a list of types and scopes found here, (b) states what changed, and (c) suffixes the related issues number. E.g. "fix(controller): Updates such and such. Fixes #1234".
• I've signed my commits with DCO
• My builds are green. Try syncing with master if they are not.
• I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
• I have run all tests locally (including the flaky ones) and they pass on my workstation
• I have used LLM/AI/Agent tools for this PR but I am responsible for all code of this PR
• I understand what the code does and WHY/HOW it works in several scenarios
• I know if my code is just adding new functionality or changing old functionality for existing users
• My organization is added to USERS.md.

[acquia-devops-ci-cd-pipeline-4]

Cortex changes preview

Location	URL
Staging	http://app.cortex.staging.cicd.acquia.io/admin/index?tag=acquia/argo-rollouts

[acquia-devops-ci-cd-pipeline-4]

⚠️ Orca Scan Vulnerabilities

status	URL
CVEs found with status: WARNING	https://cloudbees.ais.acquia.io/devops-pipeline-4-jenkins/job/KCS-argo-rollouts-PIPELINE/job/PR-27/2/cloudbees-pipeline-explorer