Integrate upgrade script into nightly build pipeline for upgrade testing

Parent Issue

Related to #30163

Task

To ensure compatibility between different versions of dotCMS, the upgrade testing script needs to be integrated into the nightly build pipeline. This will automate the testing of upgrades from various system versions to the latest main version, allowing issues to be identified early in the development cycle. Although the script has already been provided in a PR, it is not currently being executed as part of the automated build process, increasing the risk of undetected upgrade-related issues.

Tasks:

• [ ] Review and validate the upgrade testing script provided by the QA team
• [ ] Integrate the script into the nightly build pipeline.
• [ ] Configure the pipeline to:
• Log the results of each upgrade test for analysis.
• [ ] Set up notifications for any failures encountered during the upgrade testing process.

Proposed Objective

Quality Assurance

Proposed Priority

Priority 2 - Important

Acceptance Criteria

• The upgrade testing script is executed as part of the nightly build pipeline.
• Upgrades from predefined versions of dotCMS to the latest main version are tested automatically.
• Detailed logs of the upgrade process are generated and stored for review.
• Failures are reported immediately to the appropriate team members via notifications.
• The pipeline runs successfully without significant performance overhead.

Assumptions & Initiation Needs

• The upgrade testing script provided in the PR is complete and functional.
• The pipeline environment has access to all required versions of dotCMS for upgrade testing.
• Necessary permissions and configurations are available to automate the execution of the script.

Review the upgrade testing script provided in PR #30480 and the context in parent issue #30163, then locate the nightly build pipeline entry point and its version configuration. Done means predefined upgrades run nightly, detailed results are stored, and failures notify the appropriate team without significant performance overhead.