[DataAvailability] Implement fork-aware Events Endpoints

Update Events endpoints to use caching layer to get data from local storage.

• GetEventsForHeightRange
• GetEventsForBlockIDs

Implementation tasks

1. Add arguments to backend implementation that specify the user query criteria
2. Update grpc handler to extract and pass the criteria from the protobuf request
3. Update rest handler to extract and pass the criteria
4. In the backend implementation:
   a. Get the block(s) the request relates to
   b. Lookup the execution result for the provided block
   c. Get the snapshot for the result, then get the storage reader(s) required for the endpoint
   d. Use the reader as usual
5. Update error handling to use the new framework
6. Ensure godocs are up to standard for all methods that are interacted with during the code paths.

Notes:
Both of these methods allow querying a set of blocks. Since there can be forks, the API needs to ensure that all results are from the same fork. This can be done by finding the block from the range with the highest height and using it to get the result. This will be the newest descendant in the fork. From there, the snapshot will ensure that querying for additional blocks will return only data from the fork.

Start with the implementations of GetEventsForHeightRange and GetEventsForBlockIDs, then trace the corresponding gRPC and REST handlers and their protobuf requests. Follow how backend criteria, blocks, execution results, snapshots, and storage readers are passed through the endpoints, and review the linked error framework. Done means both endpoints return fork-consistent data, use the updated error handling, and have the required godoc coverage.