Add analysis-kinds input

[mbg]

This PR follows up from #3055 and adds an analysis-kinds input to the init action. This is a required input, but defaults to code-scanning so that there's no change to existing workflows. The input is parsed and the resulting analysis kinds are stored in the configuration.

The isCodeQualityEnabled function is updated to inspect that configuration, instead of the quality-queries input.

For backwards compatibility, we enable the code-quality analysis kind if there is an input to quality-queries.

Fundamentally, this PR shouldn't change the existing behaviour of the Action in any way.

Risk assessment

For internal use only. Please select the risk level of this change:

• Low risk: Changes are fully under feature flags, or have been fully tested and validated in pre-production environments and are highly observable, or are documentation or test only.

Merge / deployment checklist

• Confirm this change is backwards compatible with existing workflows.
• Consider adding a changelog entry for this change.
• Confirm the readme and docs have been updated if necessary.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[henrymercer]

Out of interest, where's this restriction coming from? We can address it in a follow up PR, but I think we want to be able to run code quality only analyses.

[mbg]

Yes, this restriction will be lifted in a follow-up PR. It's just representative of the current state of the implementation as of this PR.

The base branch was changed.