Update token dependencies

[willhickey]

In preparation for bumping the monorepo version to 2.0.0, relax some of the internal dependencies.

[CriesofCarrots]

lgtm. I think we also need to bump this crate to v2.0.1 for release, right?

Pull request has been modified.

[CriesofCarrots]

I'm actually surprised we haven't run into this before. @joncinque , have you seen any conflict issues trying to publish spl-token-2022 in the past? The token-group-interface and token-metadata-interface dependencies are probably pretty new to the monorepo, but memo has been in there forever.

This is what the conflict looked like, incidentally:

$ cargo package
   Packaging spl-token-2022 v2.0.0 (/solana-program-library/token/program-2022)
   Verifying spl-token-2022 v2.0.0 (/solana-program-library/token/program-2022)
    Updating crates.io index
error: failed to verify package tarball

Caused by:
  failed to select a version for `spl-memo`.
      ... required by package `solana-transaction-status v1.17.17`
      ... which satisfies dependency `solana-transaction-status = "=1.17.17"` of package `solana-rpc-client v1.17.17`
      ... which satisfies dependency `solana-rpc-client = "=1.17.17"` of package `solana-client v1.17.17`
      ... which satisfies dependency `solana-client = "=1.17.17"` of package `solana-banks-server v1.17.17`
      ... which satisfies dependency `solana-banks-server = "=1.17.17"` of package `solana-program-test v1.17.17`
      ... which satisfies dependency `solana-program-test = ">=1.17.17, <=2"` of package `spl-token-2022 v2.0.0 (/solana-program-library/target/package/spl-token-2022-2.0.0)`
  versions that meet the requirements `=4.0.0` are: 4.0.0

  all possible versions conflict with previously selected packages.

    previously selected package `spl-memo v4.0.1`
      ... which satisfies dependency `spl-memo = "^4.0.1"` of package `spl-token-2022 v2.0.0 (/solana-program-library/target/package/spl-token-2022-2.0.0)`

  failed to select a version for `spl-memo` which could resolve this conflict

I'm just sort of confused that we didn't see the same error publishing spl-token-2022 v0.9.0, which specifies spl-memo v4, when monorepo was on spl-memo = "=v3.0.1"

[CriesofCarrots]

Wouldn't hurt to get @joncinque 's sanity check, if he's around

[joncinque]

Sorry for the late response, but it looks good!

And I think we got lucky beforehand because cargo does support multiple concurrent major versions in some situations. So it's valid for token-2022 to use memo v4 and the monorepo to use memo v3, but it's not valid for monorepo to require =4.0.0 but for token-2022 to use 4.0.1

[CriesofCarrots]

And I think we got lucky beforehand because cargo does support multiple concurrent major versions in some situations. So it's valid for token-2022 to use memo v4 and the monorepo to use memo v3, but it's not valid for monorepo to require =4.0.0 but for token-2022 to use 4.0.1

Oh, cargo, you make no sense to my feeble human brain sometimes