feat: support versioned txs in sendTransaction and simulateTransaction

[jstarry]

Problem

Not possible to use the Connection.sendTransaction and Connection.simulateTransaction methods with versioned transactions.

Summary of Changes

• Deprecate the usage of Connection.sendTransaction and Connection.simulateTransaction without using a VersionedTransaction class.
• Deprecate the side effects of the above methods including "recentBlockhash" replacement and signing

Fixes #

[codecov]

Codecov Report

Merging #27528 (5b57610) into master (e779032) will decrease coverage by 0.9%.
The diff coverage is n/a.

❗ Current head 5b57610 differs from pull request most recent head 12d8281. Consider uploading reports for the commit 12d8281 to get more accurate results

@@            Coverage Diff            @@
##           master   #27528     +/-   ##
=========================================
- Coverage    76.9%    75.9%   -1.0%     
=========================================
  Files          48       52      +4     
  Lines        2505     2684    +179     
  Branches      355      374     +19     
=========================================
+ Hits         1927     2038    +111     
- Misses        448      510     +62     
- Partials      130      136      +6     

[steveluscher]

While we're changing the signatures anyway, maybe go full-on config object style.

/** @deprecated */
simulateTransaction(
  transactionOrMessage: Transaction | Message,
  signers?: Array<Signer>,
  includeAccounts?: boolean | Array<PublicKey>,
): Promise<...>
simulateTransaction(config: SimulateTransactionConfig): Promise<...>;
async simulateTransaction(
  transactionOrConfig: Transaction | SimulateTransactionConfig,
  signers?: Array<Signer>,
  includeAccounts?: boolean | Array<PublicKey>,
): Promise<...> {
  // ...
}

[jstarry]

Now is definitely the time to do something like that but I prefer to keep the transaction as a separate arg since it mirrors the RPC API request structure. Thanks for the suggestion though!