Release frc42_dispatch 3.0.0, frc_46 3.1.0, fvm_actor_utils 3.0.0

[alexytsu]

To release will follow these steps: #181

In future, this should be automated so that anyone with sufficient permissions on the repository can publish releases easily.

[alexytsu]

I don't have a good way to --dry-run the releases/updates here. For example, frc42_dispatch needs an updated frc42_hasher which is yet to be published.

@abright any tips to check that all the underlying dependencies that need bumping have been touched?

[coveralls]

Coverage: 83.151%. Remained the same when pulling cef67d0 on release into 13917d2 on main.

[abright]

@abright any tips to check that all the underlying dependencies that need bumping have been touched?

Not sure if there's some nice automated way to do it, I check manually but that won't scale well if there's more than a couple dependencies involved. Bumping version numbers earlier (when changes are made) would probably let cargo catch it for us, though that puts us at the mercy of cargo's resolver so maybe it wouldn't trip up if we'd only made patch-level changes or something?