update scala version settings

[xuwei-k]

Pull Request Checklist

• Have you read through the contributor guidelines?
• Have you squashed your commits?
• Have you added copyright headers to new files?
• Have you updated the documentation?
• Have you added tests for any changed functionality?

Fixes

Purpose

use semantic version selector for scala version settings in github actions.

Background Context

References

https://github.com/sbt/sbt/releases/tag/v1.7.0

++ command updates
Prior to sbt 1.7 ++ filtered subprojects using crossScalaVersions having the same ABI suffix as . This behavior was generally not well understood, and also created incorrect result for Scala 3.x since ++ 3.0.1 test could downgrade subproject that may require 3.1 or above.

sbt 1.7.0 fixes this by requiring ++ so part can be given as a semantic version selector expression, such as 3.1.x or 2.13.x. Note that the expression may match at most one Scala version to switch into. In sbt 1.7.0, a concrete version such as ++ 3.0.1 equires exact version to be present in crossScalaVersion.

[ihostage]

It's great! Thank you, @xuwei-k! 👍

[mkurz]

This works?

[mkurz]

Ah ok, just saw the PR description.

[ihostage]

@mkurz I think we should do that for other repos where it will be possible ☝️

[mkurz]

@ihostage I will release a Play milestone and will upgrade all repos with it, while doing that I can also update the workflow.