v1.16: spl: Bump token-2022 and friends (backport of #33453)

[mergify]

This is an automatic backport of pull request #33453 done by Mergify.
Cherry-pick of de38b05 has failed:

On branch mergify/bp/v1.16/pr-33453
Your branch is up to date with 'origin/v1.16'.

You are currently cherry-picking commit de38b05ad1.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   account-decoder/src/parse_token.rs
	modified:   account-decoder/src/parse_token_extension.rs
	modified:   fetch-spl.sh
	modified:   ledger/Cargo.toml
	modified:   ledger/src/token_balances.rs
	modified:   program-test/src/programs.rs
	deleted:    program-test/src/programs/spl_token_2022-0.6.0.so
	new file:   program-test/src/programs/spl_token_2022-0.9.0.so
	modified:   programs/sbf/Cargo.toml
	modified:   rpc/Cargo.toml
	modified:   rpc/src/rpc.rs
	modified:   transaction-status/Cargo.toml
	modified:   transaction-status/src/parse_associated_token.rs
	modified:   transaction-status/src/parse_token.rs
	modified:   transaction-status/src/parse_token/extension/confidential_transfer.rs
	new file:   transaction-status/src/parse_token/extension/confidential_transfer_fee.rs
	new file:   transaction-status/src/parse_token/extension/metadata_pointer.rs
	modified:   transaction-status/src/parse_token/extension/mod.rs
	new file:   transaction-status/src/parse_token/extension/transfer_hook.rs

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   Cargo.lock
	both modified:   Cargo.toml
	both modified:   account-decoder/Cargo.toml
	both modified:   programs/sbf/Cargo.lock

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

---

Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

• @Mergifyio refresh will re-evaluate the rules
• @Mergifyio rebase will rebase this PR on its base branch
• @Mergifyio update will merge the base branch into this PR
• @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

• look at your merge queues
• generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

[codecov]

Codecov Report

Merging #33465 (10cd10c) into v1.16 (d5adf45) will decrease coverage by 0.1%.
The diff coverage is n/a.

❗ Current head 10cd10c differs from pull request most recent head 547cf05. Consider uploading reports for the commit 547cf05 to get more accurate results

@@            Coverage Diff            @@
##            v1.16   #33465     +/-   ##
=========================================
- Coverage    81.9%    81.9%   -0.1%     
=========================================
  Files         763      763             
  Lines      208424   208424             
=========================================
- Hits       170898   170882     -16     
- Misses      37526    37542     +16     

[joncinque]

Since the spl crates have started using newer versions of dependencies, this backport also bumps some dependencies. I was able to reduce this down to:

• bump proc-macro2 from 1.0.59 to 1.0.60 -- the change there is very small there https://github.com/dtolnay/proc-macro2/releases/tag/1.0.60
• bump bytemuck from 1.13.1 to 1.14.0 -- the change is a bit larger and hard to track, from b19f8abfe34d6ab660e748086874c01e0212b738 to ff0b14dae9a4f0650f17c15c16acbd75df1cc4b5, see https://github.com/Lokathor/bytemuck/commits/main

If this isn't acceptable, we can probably drop it.

[CriesofCarrots]

Seems reasonable to me. Ping me after you rebase on the monorepo version bump and I'll reapprove for merge

[joncinque]

@CriesofCarrots ping!