[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

Preview Give feedback

1. [Access] Draft design of new WebSockets #6508
   S-Access +1
   
2. [Access] Implement web socket handler for new web socket connection under /ws endpoint #6593
   S-Access +1
   
3. [Access] Implement DataProvider interface and factory of data providers #6584
   S-Access +1
   
4. [Access] Change SendAndSubscribe endpoint's MessageIndex to start at 0 #6575
   Improvement S-Access +2
   
5. [Access] Add implementation for blocks, block headers and block digests data providers #6585
   3 of 3
   S-Access +1
   
6. [Access] Implement new web socket controller component #6583
   S-Access +1
   
7. [Access] Implement web socket connection mock for unit testing of web socket controller #6635
   S-Access +1
   
8. [Access] Configure ws connection in ws controller #6638
   S-Access +1
   
9. [Access] Implement keepalive routine with ping-ponging to ws connection in ws controller #6639
   S-Access +1
   
10. [Access] Design error handling for web socket connection #6642
    S-Access +1
    
11. [Access] Implement success/error response handling for each websocket action request #6724
    S-Access +1
    
12. [Access] Implement response limit tracker routine for ws controller #6640
    S-Access +1
    
13. [Access] Add client id for subscriptions #6637
    S-Access +1
    
14. [Access] Add implementation for events data providers #6588
    S-Access +1
    
15. [Access] Add implementation for accounts data providers #6587
    S-Access +1
    
16. [Access] Subscribe to tx results over ws without sending tx #6767
    S-Access +1
    
17. [Access] Add implementation for transaction status data providers #6586
    S-Access +1
    
18. [Access] Make WebSocket responses from data providers consistent with Access REST API responses. #6775
    S-Access +1
    
19. [Access] Implement inactivity tracker #6799
    S-Access +1
    
20. [Access] Implement integration test for new websockets #6641
    S-Access +1
    
21. [Access] Add documentation for new websockets #6644
    S-Access +1
22. [Access] Add examples for ws conn usages #6643
    S-Access +1
23. [Access] Deprecate old streaming event websockets endpoint #6754
    S-Access +1
24. [Access] Improve subscription Streamer functionality to graceful shutdown on demand #5561
    Preserve S-Access +2
    
25. [Access] Pending response from send and subscribe should return immediately #6573
    Improvement S-Access +2
    
26. [Access] Improve SendAndSubscribe status handling #6574
    Improvement S-Access +2
    

[Guitarheroua]

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