Add agave-reserved-account-keys crate

[jstarry]

Problem

Reserved account key set composition is subject to runtime feature gates and should live in the agave monorepo rather than creating a circular dependency between agave and the sdk repos.

Summary of Changes

• Copy in solana-reserved-account-keys
• Rename to agave-reserved-account-keys
• Update usages of solana-reserved-account-keys and solana-sdk::solana-reserved-account-keys to `agave-reserved-account-keys

Fixes #

[mergify]

If this PR represents a change to the public RPC API:

1. Make sure it includes a complementary update to rpc-client/ (example)
2. Open a follow-up PR to update the JavaScript client @solana/web3.js (example)

Thank you for keeping the RPC clients in sync with the server API @jstarry.

[jstarry]

Won't be able to merge this until the owner of this new crate is transferred to anza-team

[joncinque]

Looks great! I followed along all of the usages and confirm that this covers all of them. Thankfully the only export from the crate is ReservedAccountKeys.

I also mostly skimmed the code copied from solana-reserved-account-keys.

@yihau can you accept ownership of agave-reserved-account-keys?

[jstarry]

Won't be able to merge this until the owner of this new crate is transferred to anza-team

Actually I think we should ignore the crates check error and merge this once the rest of CI is green. Merging will allow us to prep the feature set migration change while we wait for the ownership transfer is completed. The crates check will only error on PR's that directly modify the specific Cargo.toml file so it shouldn't disrupt other devs.

[mergify]

Backports to the beta branch are to be avoided unless absolutely necessary for fixing bugs, security issues, and perf regressions. Changes intended for backport should be structured such that a minimum effective diff can be committed separately from any refactoring, plumbing, cleanup, etc that are not strictly necessary to achieve the goal. Any of the latter should go only into master and ride the normal stabilization schedule. Exceptions include CI/metrics changes, CLI improvements and documentation updates on a case by case basis.

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 94.73684% with 6 lines in your changes missing coverage. Please review.

Project coverage is 83.3%. Comparing base (381a5d5) to head (2858041).
Report is 3 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff            @@
##           master    #5513    +/-   ##
========================================
  Coverage    83.3%    83.3%            
========================================
  Files         822      823     +1     
  Lines      372278   372392   +114     
========================================
+ Hits       310348   310474   +126     
+ Misses      61930    61918    -12     

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[jstarry]

Ownership has been transferred! https://crates.io/crates/agave-reserved-account-keys