fix: handle Scala 3 nightly version for community build

[ckipp01]

This was originally reported on Discord but it looks like the "unmanaged" community build is filtering out Mill projects that use mill-tpolecat, as you can see in
https://github.com/VirtusLab/community-build3/blob/927f3751011d120c52a5217dfe8ccd3321f49c42/env/prod/config/filtered-projects.txt#L66-L69. From the comment and from playing around it looks to be because if you have a NIGHTLY or RC or anything it will puke. This adds a fallback for Scala 3 projects to revert back to the last stable release in those situations. Hopefully this will allow for those listed Mill projects to still be tested in the community build.

[carlosedp]

Awesome, thanks @ckipp01, will keep an eye here to ask them to remove project from filter once merged.

[ckipp01]

@joan38 thank you! Feel free to ping me when you cut a new release and I'll see if I can remove those repos from the community build and update those repos usages.

[joan38]

Thanks @ckipp01.
0.3.2 on it's way

[carlosedp]

Thanks Chris and Joan, I bumped the libs on riscvassembler and published v1.7.1 to address this (should be up in a couple mins).

[carlosedp]

@ckipp01 once the other two repos bump, would you open the PR removing from the filtered-projects or do you want me to do it?
Again, thanks for looking into this!

[ckipp01]

@ckipp01 once the other two repos bump, would you open the PR removing from the filtered-projects or do you want me to do it? Again, thanks for looking into this!

Once they are bumped and released I can do it. But if you notice that's done and I haven't done it yet, feel free!

[carlosedp]

Hi @ckipp01, since the other two projects haven't merged the PRs, I've sent a PR to remove my lib from the filters.
VirtusLab/community-build3#126