Make explicitly passed scala version use the latest release, not the default one

[MaciejG604]

E.g. make -S 2.13 expand to 2.13.12 even though our default for now is 2.13.11
Fixes #2394

[MaciejG604]

Tests run: https://github.com/VirtusLab/scala-cli/actions/runs/6258371552/job/16992276646?pr=2411#step:8:252

[SethTisue]

This felt weird to me at first. But after some thought, I think I've convinced myself it's actually best. We don't want the default behavior to require doing a remote query (which might take time, or be blocked by a firewall or a container setting or what have you), and we also don't want someone's Scala version to suddenly change on them unless they either explicitly requested dynamic behavior (e.g. -S 2 or the like) or they upgraded scala-cli itself.

cc @lrytz

[lrytz]

@SethTisue I don't really follow; you say "we don't want the default behavior to require doing a remote query", but IIUC this PR does that, it will query to find out what's the latest release?

[SethTisue]

@SethTisue I don't really follow; you say "we don't want the default behavior to require doing a remote query", but IIUC this PR does that, it will query to find out what's the latest release?

I meant what happens if you don't -S at all.

[lwronski]

LGTM