chore: Experiment with GCP Release Please

[arielvalentin]

An experiment to replace toys.

https://github.com/google-github-actions/release-please-action/tree/main

[arielvalentin]

@kaylareopelle if you all have any monorepos in use I could use help/pointers because this is like a very minimal configuration and I am not sure if I am holding it right.

[kaylareopelle]

I found opentelemetry-js-contrib added it in 2021: open-telemetry/opentelemetry-js-contrib#659

I think the missing piece is a release-please-config.json file: https://github.com/open-telemetry/opentelemetry-js-contrib/pull/659/files#diff-c55d4dcb68c348b2c06d263819702fbce72eeeb35b662956d02049a5a18fcf2b

[arielvalentin]

@kaylareopelle great that you found that because I implemented this incorrectly and thought the manifest JSON was the same as the config JSON file.

I pushed up a commit that sets the files with what I believe are the correct configurations now.

[kaylareopelle]

Hi Ariel! I think this looks good. I have one comment, but JIC we don't need to take action, this is approved!

[kaylareopelle]

JS has a few more keys here. Do we need them?

https://github.com/open-telemetry/opentelemetry-js-contrib/blob/cf57292853333584400850226f37fd0221cc0bfd/.github/workflows/release-please.yml#L31-L32

[arielvalentin]

I'm using built in actions tokens instead of PATs.

Built in tokens have a limitation that they don't trigger other actions if a bot performs the actions, which is why say when the bot opens a PR it does not end up triggering unit tests.

I didn't want to start using PATs because then it would be linked to one of our accounts so I figured that I'd live with the consequences and do things like have to manually run tests myself.

If we run into any issues with this flow then I'll switch to using pats.

One thing I haven't figured out yet is how to deal with dependencies yet, e.g. bumping AS and then bumping Rails then all etc...