feat: add support for 'code-quality' permission

[smlx]

I tried to integrate the new valid/invalid test examples with the existing test suite. Please let me know if I need to change anything there.

Closes: #672

[smlx]

Gentle ping @rhysd. Could I please get a review of this change? It's currently causing linting failures across any project using the code-quality permission.

[TheAlphaEngineerCode]

Reviewed the permission map and the workflow- and job-level fixtures. The new scope accepts the documented read/write/none values, and the invalid-value path is covered at both levels. I ran TestLinterLintOK and TestLinterLintError on Go 1.25.12 for Windows; both pass. The unrelated full-suite environment checks require Bash/WSL and executables allowed by Windows Application Control, so I did not treat those host-specific failures as regressions in this change.

[jacobwoffenden]

@rhysd any chance this could be merged and released so super linter can be updated? thanks!