Update buf config to v2

[emcfarlane]

Sets the buf version v1.35.0 explicitly. Runs buf config migrate. Runs buf format -w. Upgrades the bazel module to 0.3.0. Blocks #232

[rodaine]

Not sure if managed modules can handle this yet since there are two modules in here. Cc @unmultimedio

[emcfarlane]

Can push multiple v2 modules, modules without names are ignored.

[unmultimedio]

Not sure if managed modules can handle this yet since there are two modules in here. Cc @unmultimedio

You can update here to v2 no problem, we don't support v2 in the managed modules repo yet, but we can do what we did for bufbuild/confluent by setting up a static buf.yaml v1: bufbuild/modules#579

[rodaine]

I'm not sure that will work. There are two modules in here, and one depends on the other. A static buf.yaml won't work in that case.

[emcfarlane]

Closing for now.

[unmultimedio]

I'm not sure that will work. There are two modules in here, and one depends on the other. A static buf.yaml won't work in that case.

As long as there are no breaking changes it should work. The BSR syncer pulls information from all repos at the same time, but actually syncs them in dependency order, so as long as we say that pvt depends on pv, then pvt will grab the latest commit on the default label from pv which would be just synced. See this section:

To minimize issues with pinned dependencies on these modules, we sync them in the following order. First, we sync standalone modules. After they succeed, we then sync the modules that depend on them, which use the latest pushed dependency commit. As long as the dependencies don’t have any breaking change in the source code, this should be sufficient and stable for upstream modules.

https://github.com/bufbuild/modules?tab=readme-ov-file#how-we-handle-dependencies