Migrate to bloop-cli and remove module from scala-cli

[ckipp01]

Is your feature request related to a problem? Please describe.
There are currently two different forks. @alexarchambault outlined some of the steps that would be necessary to make these converge and one of them was that bloop-cli was moved to its own repo, but it may have fallen out of sync and it's not currently being used by this repo. Instead, this repo just uses it as a module inlined.

Describe the solution you'd like

• I'd like for bloop-cli and the code that is inlined to be synced up.
• I'd like for bloop-cli to be documented and released
• I'd like scala-cli to just rely on bloop-cli

Describe alternatives you've considered
Have multiple forks of bloop out there forever.

Additional context
Once we get this done, we can better explore using it in Metals, which would allow us to drop it in Bloop, simplify it, and then maybe even star the convergence project.

[alexarchambault]

I'd like to advance this as much as I could this week. Not sure what others think about it, but here is a possible path forward, that I'm working on right now (the first steps at least):

• folding scala-cli/bloop-cli into scala-cli/bloop-core: that would make all Scala CLI Bloop-related code live in a single repo, pushing both a Bloop server and a library to spawn and interact with Bloop (to Maven Central), and Bloop CLI binaries (as GitHub release assets)
• make VirtusLab/scala-cli use the library from scala-cli/bloop-core rather than its own code (need to insure that the code at scala-cli/bloop-core doesn't miss anything that VirtusLab/scala-cli has)
• add missing server-related parts in scala-cli/bloop-core (benchmarks, ability to listen on a TCP port)
• remove the backend / frontend / shared / benchmark modules from scalacenter/bloop, and depend on the ones published by scala-cli/bloop-core instead
• rename scalacenter/bloop to scalacenter/bloop-integrations, and scala-cli/bloop-core to scalacenter/bloop
• deprecate the CLI generated in scalacenter/bloop-integrations

That's only a proposal of a path forward for now, as I guess we'll need to agree on the last steps in particular 😅

But to summarize, I basically propose to make the current Scala CLI Bloop fork the new default Bloop server, to make the Scala CLI Bloop libraries and CLI the new default Bloop libraries and CLI, and to leave only integrations in the current Bloop repo.

[alexarchambault]

Then in a second time, we could have Metals use the new Bloop library rather than the current launcher module from scalacenter/bloop (basically what scalameta/metals#4103 attempts to do), and remove the launcher and bloopgun modules, and the former CLI, from scalacenter/bloop.

[alexarchambault]

An update on this:

• Add bloop-cli modules scala-cli/bloop-core#136 moved the bloop-rifle-related modules from scala-cli/bloop-cli to scala-cli/bloop-core
• Add last Scala CLI repo updates scala-cli/bloop-core#139 updated the bloop-rifle sources in scala-cli/bloop-core
• scala-cli/bloop-cli is now archived
• Use bloop-rifle module from scala-cli/bloop-core repo #1989 makes Scala CLI use bloop-rifle from scala-cli/bloop-core, and removes it from the Scala CLI sources
• [POC] Start Bloop using bloop-rifle from Scala CLI… scalameta/metals#4103 makes Metals use bloop-rifle from scala-cli/bloop-core
• Remove Bloop server modules scalacenter/bloop#2027 removes the server modules from the upstream Bloop repository, so that these only live in scala-cli/bloop-core