Use separate CodeQL workflow files for each language

Discussion below:

> Do we need to add more languages here?

Let us get this PR merged first before we add more languages and checks.

For example if we add the Java language to the matrix we may also need to implement "paths" or only run the Java CodeQL check when certain files change. These checks can sometimes take a while to run on the CI.

Also it is probably best to separate each language that we want to check into its own CodeQL workflow file and add all the "paths". For example:

- java-codeql-analysis.yml
- python-codeql-analysis.yml
- actions-codeql-analysis.yml
- etc

Using separate CodeQL workflow files for each language in a multi-language repository allows for tailored analysis and build processes. This approach is particularly useful when languages have different build requirements or when you want to apply specific queries or configurations to individual languages.

Our current analysis file:

https://github.com/apache/cloudstack/blob/main/.github/workflows/codeql-analysis.yml

_Originally posted by @jbampton in https://github.com/apache/cloudstack/pull/11300#discussion_r2352998006_

Inizia con .github/workflows/codeql-analysis.yml e con la discussione della pull request 11300. Identifica i linguaggi attualmente coperti e i percorsi dei file che dovrebbero attivare ciascun controllo. Il lavoro è completato quando ogni linguaggio dispone di un proprio file di workflow CodeQL con i percorsi appropriati e una configurazione specifica per il linguaggio.

Scritto dal modello di indicizzazione a partire dal testo della issue.