When provided w --release-version parameter, query job should use it to override the version stored in settings.yaml

[philipjyoon]

Checked for duplicates

Yes - I've already checked

Describe the bug

For HLS, SLC, and CSLC queries, --release-version parameter is now optional. We use the release version stored in settings.yaml because we would (almost) never use more than one version of PCM software in a cluster.

Regardless, we should still use the value provided in --release-version parameter if it's being used because that's the user's wish.

Workaround: change RELEASE_VERSION in settings.yaml if running query from the Mozart box which is by far the most common use-case.

What did you expect?

I expected [...]

Reproducible steps

1.
2.
3.
...

Environment

- Version of this software [e.g. vX.Y.Z]
- Operating System: [e.g. MacOSX with Docker Desktop vX.Y]
...