Feature #366 main_v2.1 sonarqube gha

[JohnHalleyGotway]

Same set of changes from PR #367, but these are for the main_v2.1 branch. I'm updating the main_v2.1 branch to make the SonarQube workflow dispatch option available and also to update the PR template to include the reminder about checking the SonarQube status during PR reviews.

FYI, I was easily able to apply the exact same changes for the main_v2.1 using the git cherry-pick command.

In my feature_366_develop_sonarqube_gha I ran git log -v to see my history of commits... with the commit message and commit hash. On my new feature_366_main_v2.1_sonarqube_gha branch, I ran the following command:

git cherry-pick \
  c543737bcca77371133e64e9b8eb5920a70c30b5 \
  ca2dfba9e78a29385baaa27e7e3ad2b023f7750a \
  86584e09c209db65a70d943bd7a4940cba312a07 \
  cbf219a5d3261cadf886b29787783f52ace831e2 \
  742a5ba951ce7be50c808b800ff1b9db488fe4b8

That applied all the changes across those 5 commit hashes to my new branch and was much faster and less error-prone that making the same commits manually.

Although, since I'm paranoid, I ran the following commands to make sure there were no unexpected changes:

# On feature_366_develop_sonarqube_gha
git diff origin/develop > develop_diffs
# On feature_366_main_v2.1_sonarqube_gha
git diff origin/main_v2.1 > main_diffs
diff develop_diffs main_diffs

And the set of diffs were identical.