Create nightly tests for extension workflows in branch 'master'

[aalves08]

Summary

Fixes #12159
Fixes #12032

Based on the work done in aalves08#4

Occurred changes and/or fixed issues

• Create nightly tests for extension workflows in branch master
• Create nightly tests for extension workflows in branch release-2.9 - needs Adjust extension workflows in branch 'release 2.9' for nightly run tests for extensions #12603
• Create nightly tests for extension workflows in branch release-2.8 - needs Adjust extension workflows in branch 'release 2.8' for nightly run tests for extensions #12604
• Created script to gather info from branch about Shell, Creators and extension to be used in tested on ui-plugin-examples
• Added necessary adjustments in workflows for them to testable in master

Note: Necessary github secret has already been added to the repo

Technical notes summary

Example of a workflow run with a failure in a job: https://github.com/aalves08/dashboard/actions/runs/11817619114 + https://github.com/aalves08/dashboard/actions/runs/11817619114/job/32923438990
Example of a workflow run with all jobs succeeded: https://github.com/aalves08/dashboard/actions/runs/11817653117 + slack message: https://github.com/aalves08/dashboard/actions/runs/11817653117/job/32923642602

Key takeaways

• Reusable workflows can only be run with literals, therefore running it as a matrix won't work
• Reusable workflows can only be can only be called from jobs, not steps
• Only a job has knowledge about it's job.status. In parallel jobs, each aren't aware of the success/failure of their siblings -> https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/accessing-contextual-information-about-workflow-runs#job-context
• Job status (failure/success) information needs to be propagated in order to be used in other jobs

Areas or cases that should be tested

Areas which could experience regressions

Screenshot/Video

Checklist

• The PR is linked to an issue and the linked issue has a Milestone, or no issue is needed
• The PR has a Milestone
• The PR template has been filled out
• The PR has been self reviewed
• The PR has a reviewer assigned
• The PR has automated tests or clear instructions for manual tests and the linked issue has appropriate QA labels, or tests are not needed
• The PR has reviewed with UX and tested in light and dark mode, or there are no UX changes