Bugfix: Correct the branch name for the SonarQube scanning nightly

[hsoh-u]

Replace italics below with details for this issue.

The default branch name for the SonarQube scanning is "master". It should be changed to "develop" branch.

Describe the Problem

Provide a clear and concise description of the bug here.

The branch name for the MET nightly build is "master", not "develop.

Expected Behavior

Provide a clear and concise description of what you expected to happen here.

It should be "develop" branch

Environment

Describe your runtime environment:
1. Machine: Linux Workstation
2. OS: RedHat Linux
3. Software version number(s) - MET 11.1 (develop branch) & SonarQube server 9.6.x

To Reproduce

Describe the steps to reproduce the behavior:

1. Connect VPN (if necessary)
2. Open a web browser
3. Access following URL
   http://mandan.rap.ucar.edu:9000/dashboard?id=org.sonarqube%3AMET_develop_NB

Post relevant sample data following these instructions:
https://dtcenter.org/community-code/model-evaluation-tools-met/met-help-desk#ftp

Relevant Deadlines

List relevant project deadlines here or state NONE.

Funding Source

2771021 AF METplus

Define the Metadata

Assignee

• Select engineer(s) or no engineer required
• Select scientist(s) or no scientist required

Labels

• Select component(s)
• Select priority
• Select requestor(s)

Projects and Milestone

• Select Organization level Project for support of the current coordinated release
• Select Repository level Project for development toward the next official release or add alert: NEED PROJECT ASSIGNMENT label
• Select Milestone as the next bugfix version

Define Related Issue(s)

Consider the impact to the other METplus components.

• METplus, MET, METdataio, METviewer, METexpress, METcalcpy, METplotpy

Bugfix Checklist

See the METplus Workflow for details.

• Complete the issue definition above, including the Time Estimate and Funding Source.
• Fork this repository or create a branch of main_<Version>.
  Branch name: bugfix_<Issue Number>_main_<Version>_<Description>
• Fix the bug and test your changes.
• Add/update log messages for easier debugging.
• Add/update unit tests.
• Add/update documentation.
• Push local changes to GitHub.
• Submit a pull request to merge into main_<Version>.
  Pull request: bugfix <Issue Number> main_<Version> <Description>
• Define the pull request metadata, as permissions allow.
  Select: Reviewer(s) and Development issue
  Select: Organization level software support Project for the current coordinated release
  Select: Milestone as the next bugfix version
• Iterate until the reviewer(s) accept and merge your changes.
• Delete your fork or branch.
• Complete the steps above to fix the bug on the develop branch.
  Branch name: bugfix_<Issue Number>_develop_<Description>
  Pull request: bugfix <Issue Number> develop <Description>
  Select: Reviewer(s) and Development issue
  Select: Repository level development cycle Project for the next official release
  Select: Milestone as the next official version
• Close this issue.