[Execution] Return OutOfRange instead of Internal when account block is not cached

[peterargue]

Closes: #4916

Currently, when an Access node calls GetAccount* with a block that is no longer in the EN's trie, it returns codes.Internal. This PR adds a sentinel and updates the handler to instead return codes.OutOfRange.

This will ensure that the new grpc circuit breaker available on ANs does not incorrectly classify these responses.

[codecov-commenter]

Codecov Report

Attention: 9 lines in your changes are missing coverage. Please review.

Comparison is base (3704b14) 52.97% compared to head (f2c1d6d) 55.83%.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #4917      +/-   ##
==========================================
+ Coverage   52.97%   55.83%   +2.85%     
==========================================
  Files         754      945     +191     
  Lines       68131    88261   +20130     
==========================================
+ Hits        36095    49279   +13184     
- Misses      29316    35273    +5957     
- Partials     2720     3709     +989     

Flag	Coverage Δ
unittests	55.83% <55.00%> (+2.85%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files	Coverage Δ
engine/execution/scripts/engine.go	40.00% <72.72%> (ø)
engine/execution/rpc/engine.go	53.38% <33.33%> (ø)

... and 195 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[zhangchiqing]

This is not the only place returning this error, queryExecutor.ExecuteScript could also possibly return pruned error, because it's possible state commitment is pruned after this execState.HasState check and before the queryExecutor.ExecuteScript call.

In other words, we also need to handle the pruned error from e.queryExecutor.ExecuteScript

[zhangchiqing]

I can handle it in storehouse