feat: Create rules_release

[mvgijssel]

closes #603

ref #451

ref #571

The flow

write file: https://github.com/changesets/changesets/tree/main/packages/write changelog content: https://github.com/changesets/action/blob/main/src/utils.ts#L37

• [x] Figure out calling dependencies with bzlmod: getting "No repository visible as '@aspect_rules_js' from main repository" (https://bazelbuild.slack.com/archives/C014RARENH0/p1698918118051159, https://github.com/aspect-build/rules_js/pull/1342)
• [x] Setup bazel-diff script which runs against latest master
• [x] Restructure files like rules_python or rules_py
• [x] Setup release rule which stores information about the release
• [x] Parse command line arguments in the runner (https://github.com/tj/commander.js#installation)
• [x] Setup generator command which generates changesets file for each release
• [x] Support for external repositories, like rules_task and rules_release itself?
• [x] Refactor using repositories and action classes
• [x] Refactor to use ESM
• [x] Setup version command which versions the release version files based on changesets data
• [x] Link changelog files
• [x] Publish bunq2ynab image to GitHub container registry
• [x] Publish bunq2ynab to GitHub releases
• [x] Cleanup package.json
• [x] Remove rules_task release / rules_release release
• [x] Implement publish command
• [x] Commit files and push to master
• [x] Change committing user to vgijssel-bot
• [x] Set the right branch for pushing git

API example

load("@rules_release//:defs.bzl", "release", "release_manager")

release(
  name = "bunq2ynab_release",
  version_file = "version.txt", # version file gets bumped with a new version
  target = ":bunq2ynab_image", # the Bazel target that if changed will trigger a new release (up to contributor to decide if it's "patch", "minor" or "major"
  publish = [":bunq2ynab_image_push", ":publish_github_release"], # commands to run when publishing a new release
)

# The release manager will collect all the release information and act accordingly
release_manager(
  name = "release_manager",
  deps = [
    ":bunq2ynab_release",
  ]
)

[mvgijssel]

As a strategy to get the version bumps from changesets:

1. Create tmp/changesets directory
2. For each release target create a directory like
   • tmp/changesets/rules_task
   • tmp/changesets/bunq2ynab

3. Within those directories generate a package.json which is marked as private to prevent publishing

   1. Set the version attribute to the value of the version file of the release rule
   2. Using Bazel figure out dependencies and add them to the package file like

    "dependencies": {
      "rules_task": "workspace:^"
   }

4. Setup appropriate pnpm-workspace.yaml to target tmp/* (can we live without this file?)
5. Run changeset version
6. Copy the values from the updated package version back into the release rule version file

[mvgijssel]

Bazel query commands:

Find all the recursive source files (including external) of the rules_task workspace

bazel query --noimplicit_deps --notool_deps 'kind("source file", deps(@rules_task//...))'