Automatically generate and push release info to R2 bucket on every release

[kevinmingtarja]

Description

• Made a new script (/tools/release-info) to generate modus-all.json, modus-preview.json, modus-preview-all.json, and modus-preview.json,
• Copied most of the code from /cli/src/util/versioninfo.ts, most of which should be removed in remove all github api call references, add prerelease support to CLI #545
• Created release-info, which is a standalone workflow that can be invoked both manually (workflow_dispatch) and from another workflow (workflow_call), which in our case is release-cli, release-runtime, release-sdk-as, and release-sdk-go,
• This workflow simply compiles and runs the script, and pushes the four JSON files to our releases R2 bucket

Checklist

• Code compiles correctly and linting passes locally
• Entry added to the CHANGELOG.md file describing and linking to this PR

[jairad26]

if it makes it easier, we could merge the PR #545 into this branch and close it so that we dont need another pr to remove the old versioninfo code from this as well. also this would mean theres now 2 places to maintain versioninfo.ts? i think we should be able to reference the existing one?

[kevinmingtarja]

if it makes it easier, we could merge the PR #545 into this branch and close it so that we dont need another pr to remove the old versioninfo code from this as well. also this would mean theres now 2 places to maintain versioninfo.ts? i think we should be able to reference the existing one?

i think the contents of the two would have little to no overlap right? the new one here would only have the github API related code, while in the other only the releases JSON related code.

[jairad26]

i think the contents of the two would have little to no overlap right? the new one here would only have the github API related code, while in the other only the releases JSON related code.

Ah I see yea you’re right