feat: buf bsr

[moritzzimmer]

what

PoC to test buf's maven remote packages (see https://buf.build/docs/bsr/remote-packages/maven/).

see https://buf.build/stroeer/tapir/assets/main for assets

learnings

✅ buf's remote packages are separated for proto and grpc per default
✅ packages build for various proto and grpc versions are available
✅ we could remove the java package release process in tapir and simplify our tools
✅ tested in a gRPC go project: stroeer/go-tapir#35
✅ registries for TypeScript, python and Swift are available as well (not tested in this poc)
✅ automatic documentation is nice and we could simplify our docs toolchain, see https://buf.build/stroeer/tapir/docs/main

🟡 we can't specifiy custom tag values for default buf push GitHub action (we could create a custom make target though)
🟡 might be free (see plans), according to buf beta price it would cost $34.00/month for Teams plan which doesn't add much value
🟡 buf is a startup and might run out of money

❌ packages names are different (see large diff in https://github.com/stroeer/paperboy/pull/1984) and can't be changed easily atm, see bufbuild/plugins#636

outcome

• I would push to the BSR at least to use the documentation
• using remote SDKs could be a huge simplification of out tool chain

[moritzzimmer]

superseeded by #553