Releases are triggered by code review

~~- The Github CI should be given permissions to publish to crates.io~~
~~- Merged results on `main` should be used~~
~~- Tags should be used to trigger the releases and mark the commit that was built~~

## Done Criteria
The to-be-created release steps outlined in https://github.com/filecoin-project/builtin-actors/issues/1566 can be followed without requiring manual clicking in the GitHub UI. Instead, releases should occur as a result of an approved PR.

## Why Important
1. Less time used by maintainers
2. Not bottleneck on certain folks to publish
3. Less error prone

## User/Customer
Maintainers

## Notes
1. This is more of a standard Rust repo and should be published to crates.io