fix: Added test.exclusions parameter and set default values

[pierantoniomerlino]

This pull request updates the continuous integration pipeline to improve SonarQube analysis configuration, specifically by introducing a new parameter for test exclusions and enhancing validation and documentation. The main changes focus on allowing separate configuration of source and test file exclusions for Sonar analysis, improving security checks, and updating documentation.

SonarQube Analysis Configuration:

• Added a new testExclusions parameter to the Sonar configuration, allowing users to specify test paths to be excluded from Sonar analysis. The default value is set to **/*.java,*.xml. [1] [2]
• Updated the pipeline to pass both sonar.exclusions and sonar.test.exclusions to the SonarQube analysis step, ensuring both source and test exclusions are respected.

Validation and Security:

• Enhanced input validation to check that testExclusions is a string and does not contain potentially dangerous characters, similar to the existing check for exclusions.

Documentation:

• Updated the documentation in continuousIntegrationPipeline.md to describe the new testExclusions parameter, its default value, and its purpose.