[21286] Remove CodeQL cron and other branch triggers

[JesusPoderoso]

Description

Even though 2.2.x is a master mirror, it should not contain other branches triggers for CI, neither cron expressions (non-default branch).
This PR removes them.

Contributor Checklist

• Commit messages follow the project guidelines.
• N/A The code follows the style guidelines of this project.
• N/A Tests that thoroughly check the new feature have been added/Regression tests checking the bug and its fix have been added; the added tests pass locally
• N/A Any new/modified methods have been properly documented using Doxygen.
• N/A Changes are backport compatible: they do NOT break ABI nor change library core behavior.
• N/A Changes are API compatible.
• N/A New feature has been added to the versions.md file (if applicable).
• N/A Applicable backports have been included in the description.

Reviewer Checklist

• The PR has a milestone assigned.
• The title and description correctly express the PR's purpose.
• Check contributor checklist is correct.
• Check CI results: changes do not issue any warning.
• Check CI results: CI pass and failing tests are unrelated with the changes.

[EduPonz]

Besides que conflicts I don't see why we'd run this only for 2.2.x and not master. IMO what we should do is:

1. Run on PRs review request independently of the branches (same as CI). For this we'd need a partial backport of this in all supported branches.
2. Run the analysis nightly on all the supported branches (which I think is possible without reusable workflows on any kind)

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.