Releases are triggered by code review

[alexytsu]

- 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 filecoin-project/builtin-actors#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

[BigLep]

If I had my permissions, I would change this issue such that:

Issue title

Releases are triggered by code review

Issue description

Done Criteria

The to-be-created release steps outlined in filecoin-project/builtin-actors#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