feat(ci): Add release workflow

[phated]

Related issue(s)

(If it does not already exist, first create a GitHub issue that describes the problem this Pull Request (PR) solves before creating the PR and link it here.)

Prerequisite to adding automated releases as per #19 (Need to discuss how much we actually want automated).

Description

This adds Release Please to the project. The setup is different from the noir repo because we want to track changes to each package independently. We do this with the cargo-workspace plugin, but we also want all versions to stay in-sync so we use the linked-versions plugin to ensure that.

We also want to track all changes in a changelog in the project root so we have a "simple" releaser pointing at the root directory.

You can see an example of the Release Please PR at phated#1

Summary of changes

(Describe the changes in this PR. Point out breaking changes if any.)

Dependency additions / changes

(If applicable.)

Test additions / changes

(If applicable.)

Checklist

• I have tested the changes locally.
• I have formatted the changes with Prettier and/or cargo fmt with default settings.
• I have linked this PR to the issue(s) that it resolves.
• I have reviewed the changes on GitHub, line by line.
• I have ensured all changes are covered in the description.

Additional context

(If applicable.)

[phated]

I just realized I wanted to double-check your bootstrap sha. 1 second.

[phated]

It looks like 97149ad is the release of 0.4.1 🎉