[EPIC] Bloop Next Steps

[kpodsiad]

Based https://contributors.scala-lang.org/t/bloop-next-steps/5554. These changes should simplify working with Bloop and ease the maintenance burden on any current and future contributors.

TODO:

• publish bloop launcher artifacts for Scala 2.13 - Launcher 213 #1646
• use upstream Zinc instead of forked one - Update Zinc to 1.6.0 and drop the fork #1662
• bump used Scala and sbt versions to the newest ones chore: bump scala 2.12 and 2.13 minor versions #1670, chore: bump sbt version #1679
• remove modules which are no longer needed - Remove obsolete modules #1650
• rewrite generation of the test projects to not happen on sbt load fix: move resource generation out from onLoad #1708, fix: stabilize test project resources generation #1715
• remove custom shading plugin and use sbt-shading if possible
  • refactor: stop shading launcher and bloopgun #1961
• migrate from sbt-release-early to sbt-ci-release
  • refactor(ci): migrate to sbt-ci-release #1962
  • refactor(ci): update graal release infrastructure #1966
• add Scala steward chore: Add Bloop to Scala Steward VirtusLab/scala-steward-repos#55
• move config out to separate repository to be released independently
  • https://github.com/scalacenter/bloop-config
  • refactor: start using bloop-config as a dependency #1868
• move integrations to separate repositories, where they can be released independently.
  • https://github.com/scalacenter/bloop-maven-plugin
  • https://github.com/scalacenter/gradle-bloop
  • refactor: move the Maven plugin out of Bloop #1948
  • refactor: migrate Gradle integration out of Bloop #1951
• create a community suite (most likely some modification of buildpress) that would test out some of the more popular repositories.
• make benchmarks easier to run and use.
• investigate tests and try to make them less flaky
• migrate to Monix 3.x
• upgrade bsp4s (blocked on Monix upgrade)
• simplify the meta meta build
  • refactor: rework/rethink the meta meta build stuff #1956

[tgodzik]

Thanks for putting it into an actual issue! I should have done it previously after the post on contributors.