[build] Refine checkReleasedTastyVersion logic to handle using unstable reference version of a new minor

[WojciechMazur]

In #22786 we've followed the process and updated referenceVersion to latest released version which happens to be 3.7.0-RC1 producing TASTY 28.7-experimental-1.
All nightly version when patch > 0 should be using TASTy version incremented by 1, in case of unexpected binary breakage. However non-bootstrapped tests (eg. FromTastyTest) would fail if we'd increase tasty version to 28.8-experimental-1 because these require the produced and consumed Scala files (eg. in FromTastyTest) to either:

• be produced by older stable compiler
• produced with exactly the same TASTy version

Because of that we're adding special case to checking version of released tasty to allow using the same tasty format as unstable reference version if the reference version is the RC release of new minor (patch == 0)

Fixes #22788

[skip ci]