Publish updated packages to crates.io

[dtbuchholz]

Our published crates are outdated and pointing to the old testnet. Thus, anyone using the Rust SDK will run into problems.

Note: There's likely not a ton of developers using the Rust SDK, so it's not an immediate need but would be nice. E.g., we use the Rust SDK in recallnet/js-recall#341, but we can get around the issue with a github link + rev hash dependency definition.

[joewagner]

This is related to #17

It has been a while since I was working on this, but I don't think the published crates have ever really worked.
Even though you can do cargo add recall_sdk, I don't think you were able to build anything meaningful. I setup a Hello Recall app back in April using only crates (no github), and it would not work without the changes in #261, recallnet/ipc#580, and recallnet/builtin-actors#22.

We can potentially fixup those pull requests and republish based on those changes, but the last discussion I was part of made that sound like a lower priority than the comp stuff.

For details on why crates doesn't work this comment is of note: https://github.com/recallnet/ipc/pull/580/files#r2037946822

[stbrody]

Is this going to be a problem for the work @islamaliev is doing on the synchronizer to write competition data to the testnet?

[dtbuchholz]

nah, you can use github link + rev hash to get the latest sdk in Cargo.toml deps (iirc that's what he had to do to get things to work)