Feature #2270 new_sonarqube

[hsoh-u]

Expected Differences

The SonarQube server is updated at mandan (8.9.6.50800 to 9.6.1.59531).

The SonarQube includes version numbers to the path. The softlink is used to SonarQube configuration instead of real path with version number.

drwxr-sr-x 6 met_test rap         4096 May  7  2021 /d1/projects/SonarQube/sonar-scanner-4.6.2.2472-linux
drwxr-sr-x 6 met_test rap         4096 Feb 22  2022 /d1/projects/SonarQube/sonar-scanner-4.7.0.2747-linux
lrwxrwxrwx 1 met_test rap           30 Sep 23 14:05 /d1/projects/SonarQube/sonar-scanner-linux -> sonar-scanner-4.7.0.2747-linux

The future upgrade will be done without changing the MET configuration by updating the soft link.

• Do these changes introduce new tools, command line arguments, or configuration file options? [No]
  
  If yes, please describe:
  

• Do these changes modify the structure of existing or add new output data types (e.g. statistic line types or NetCDF variables)? [No]
  
  If yes, please describe:
  

Pull Request Testing

• Describe testing already performed for these changes:
  

None, deployed to seneca

• Recommend testing for the reviewer(s) to perform, including the location of input datasets, and any additional instructions:
  

None

• Do these changes include sufficient documentation updates, ensuring that no errors or warnings exist in the build of the documentation? [No]

• Do these changes include sufficient testing updates? [No]

• Will this PR result in changes to the test suite? [No]
  
  If yes, describe the new output and/or changes to the existing output:
  

• Please complete this pull request review by [Fill in date].
  

Pull Request Checklist

See the METplus Workflow for details.

• Review the source issue metadata (required labels, projects, and milestone).
• Complete the PR definition above.
• Ensure the PR title matches the feature or bugfix branch name.
• Define the PR metadata, as permissions allow.
  Select: Reviewer(s)
  Select: Organization level software support Project or Repository level development cycle Project
  Select: Milestone as the version that will include these changes
• After submitting the PR, select Development with the original issue number.
• After the PR is approved, merge your changes. If permissions do not allow this, request that the reviewer do the merge.
• Close the linked issue and delete your feature or bugfix branch from GitHub.

[JohnHalleyGotway]

This one line version change looks fine to me! Thanks.