Allow exclusions to be array of strings

[tyler-mastery]

PR Checklist

Please check if your PR fulfills the following requirements:

• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?
Currently, exclusions are defined as a long comma-separated string. Since JSON does not support multi-line strings, this makes the configuration difficult to read, maintain, and validate with linting tools.

To improve readability and maintainability, we should allow exclusions to be specified as an array of strings. This will enable proper linting, formatting, and make large exclusion lists much easier to work with.

Example — Current (hard to read):

{
  "exclusions": "error1, error2, error3, error4, error5, error6, another, thisIsGettingLong, okThisIsReallyTooLong, iHateThisExtremelyLongString"
}

Example — Proposed (clean and readable):

{
  "exclusions": [
    "error1",
    "error2",
    "error3",
    "error4",
    "error5",
    "error6"
  ]
}

This approach makes the configuration more maintainable and aligns with best practices for managing lists in JSON.

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Configuration related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

Which package are you modifying?

• @koliveira15/nx-sonarqube
• docs-site

What is the current behavior?

Only string for exclusions

Closes #

What is the new behavior?

Allows array of strings for exclusions

Does this PR introduce a breaking change?

• Yes
• No

Other information