Hardcord state offset values to save gas and execution time

[mininny]

Description

Multiple functions are implemented to calculate the state offset of a given field. However, the offset of a field depends on the offset of the previous field until reaching the first offset. As a given offset depends on the previous offset, the code consumes a lot of gas for values that will never change.

For example, calling stateOffsetPreimageKey would consume approximately 444 gas while stateSize consume 1096 gas. Both will always return the same value.

Note that Go slow and fast implementations do not need this type of optimization as computations are cheaper.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 61.89%. Comparing base (8ff9318) to head (f733dcd).

Additional details and impacted files

@@           Coverage Diff           @@
##           master      #98   +/-   ##
=======================================
  Coverage   61.89%   61.89%           
=======================================
  Files          27       27           
  Lines        4091     4091           
=======================================
  Hits         2532     2532           
  Misses       1427     1427           
  Partials      132      132           

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

[refcell]

Verified the arithmetic - think it would be more concise for these to be constants instead of functions, but that can be a good candidate for a follow up pr.