[minor] Support db2 v12 upgrade

[terc1997]

1. Description

To support Db2 v12 upgrade, it requires to change mas update command to allow the upgrade according with the user input. So, for that support it will be included:

• --db2-v12-upgrade and --db2-license-file flag in the mas update command line
• db2_v12_upgrade and db2_license_file flag in mas_update Tekton task, backed up by a change in the ansible-devops to carry db2_v12_upgrade
• Update unit tests

Also in this PR it will be delivered the support for Db2 License file. To support that:

• Create db2LicenseFile() which has the same features as slsLicenseFile().
• It was created a new workspace shared-db2 that mounts pipeline-db2-license secret.

2. Dependencies

• [minor] Support db2 v12 upgrade ansible-devops#2140
• [minor] Support db2 v12 upgrade python-devops#204

3. Upgrade Tests

3.1. CLI Help

3.2. Non interactive

Without --db2-v12-upgrade

Without --db2-license-file

Normal flow

3.3. Interactive

4. Install tests with License

CLI Help

Interactive

Non Interactive

Pipeline with License

Pipeline without License

FVT Tests

• db2upgrade3
• db2instance

---

⚠️ Notes for Reviewers

• Ensure you have understood the PR guidelines in the Playbook before proceeding with a review.
• Ensure all sections in the PR template are appropriately completed.

[durera]

In the screenshots, it doesn't show how the user will be prompted for the db2 activation key in interactive or non-interactive ... I assume that in there though, otherwise upgrade would take them to a trial license? And we need to prevent the update being started in the event that they don't provide the activation key -- even if they think they want to move to the trial license, I just don't want that headache when it means a prod system goes offline in 30 days :D

We can let people install NEW without a license, but for the update/db2 v12 upgrade I think we need to ensure that there's no "downgrade" from full to trial as part of this action

[terc1997]

In the screenshots, it doesn't show how the user will be prompted for the db2 activation key in interactive or non-interactive ... I assume that in there though, otherwise upgrade would take them to a trial license? And we need to prevent the update being started in the event that they don't provide the activation key -- even if they think they want to move to the trial license, I just don't want that headache when it means a prod system goes offline in 30 days :D

We can let people install NEW without a license, but for the update/db2 v12 upgrade I think we need to ensure that there's no "downgrade" from full to trial as part of this action

Okay. I didn't enforce the license for db2 v12 upgrade. Let me update CLI and ansible-devops to enforce the presence during the upgrade.

[terc1997]

Added license enforcing when updating from v11 to v12.