[Epic] [Access] Enable websocket support for new streaming endpoints

[peterargue]

Why

Unblocks streaming endpoints for FCL and will improve user experience with faster transactions

To add support for these new gRPC streaming endpoints to FCL, we will need to add websocket endpoints

• blocks
• transaction statuses
• account statuses

How will we measure success

• Websocket support on ANs are released to testnet and ready for deployment on mainnet

DACI

D: Krok team
A: Peter
C: Flow team, Jeff
I: Flow team

Estimate: ~3 person months

Tasks

Beta Give feedback

1. [Access] Draft design of new WebSockets #6508
   S-Access +1
   
2. [Access] Refactor websockets streaming to support multiple subscriptions
3. [Access] Add streaming blocks subscription
4. [Access] Add streaming tx status subscription
5. [Access] Add streaming account status subscription
6. [Access] Add streaming event subscription
7. [Access] Deprecate old streaming event websockets endpoint
8. [Access] Improve subscription Streamer functionality to graceful shutdown on demand #5561
   Preserve S-Access +2
   
9. [Access] Pending response from send and subscribe should return immediately #6573
   Improvement S-Access +2
10. [Access] Improve SendAndSubscribe status handling #6574
    Improvement S-Access +2
11. [Access] Change SendAndSubscribe endpoint's MessageIndex to start at 0 #6575
    Improvement S-Access +2

[Guitarheroua]

Here is investigation for future possible refactoring of current WebSocket: WebSocket Subscriptions with a Single Connection