Migrate to using solana_transaction_context crate

[jstarry]

Problem

The solana_sdk::transaction_context module was deprecated in anza-xyz/solana-sdk#95 so we should stop using it before updating to newer versions of solana-sdk

Summary of Changes

Switch over to solana-transaction-context where appropriate

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.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 83.3%. Comparing base (e1162f7) to head (e6226aa).

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #5525   +/-   ##
=======================================
  Coverage    83.3%    83.3%           
=======================================
  Files         829      829           
  Lines      373648   373648           
=======================================
+ Hits       311541   311568   +27     
+ Misses      62107    62080   -27     

🚀 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.

[joncinque]

Looks good!

[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.