fix(validation): validate constraints

[jamietanna]

Changes

To provide better coverage for our users of what is a valid option for a
constraints value, we can validate the overall format of the
constraints block, as well as the given names of constraints.

Where we have a Tool defined, we can use the default versioning for that
Tool to validate the constraint's value.

For now, both the validation of the constraints' value, and the
validation of constraints' names will be a warning, but in the future
may be made an error.

Context

Please select one of the below:

• This closes an existing Issue: Closes #
• This doesn't close an Issue, but I accept the risk that this PR may be closed if maintainers disagree with its opening or implementation

AI assistance disclosure

Did you use AI tools to create any part of this pull request?

Please select one option and, if yes, briefly describe how AI was used (e.g., code, tests, docs) and which tool(s) you used.

• No — I did not use AI for this contribution.
• Yes — minimal assistance (e.g., IDE autocomplete, small code completions, grammar fixes).
• Yes — substantive assistance (AI generated non‑trivial portions of code, tests, or documentation).
• Yes — other (please describe):

Documentation (please check one with an [x])

• I have updated the documentation, or
• No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

• Code inspection only, or
• Newly added/modified unit tests, or
• No unit tests but ran on a real repository, or
• Both unit tests + ran on a real repository

The public repository:

[jamietanna]

@viceice if I merge this as-is, will this cause issues for other PRs? This looks like an existing coverage issue

[viceice]

@viceice if I merge this as-is, will this cause issues for other PRs? This looks like an existing coverage issue

I don't think so, but can you fix the coverage issues with ignore and to-do comments?

[jamietanna]

@viceice any help with this coverage? I can't seem to craft the right v8 ignores to make it work 🤔

[viceice]

move before first if and use ignore else

[jamietanna]

Seems to not like it

[RahulGautamSingh]

Shouldn't we also validate additionalConstraints values as well?

[jamietanna]

Shouldn't we also validate additionalConstraints values as well?

They're handled under if (!isConstraintName(k)) {

We can't validate them further as they're not as well defined in terms of what the constraint should look like, versioning wise