Add support for non-mainnet request cache validation thresholds

[fselmo]

What was wrong?

closes #3506

How was it fixed?

• If non-mainnet ethereum, allow the use of an integer value for the request cache validation threshold. Pre-configure "safe" default values for some common non-mainnet chain ids based on their varied finality mechanisms.
• This integer value represents the number of seconds from time.now() that the request cache deems as a safe enough time window to allow the request to be cached.
• Update the tests to reflect these changes.
• Added comprehensive testing around the caching logic, affected endpoints, and all relevant providers.

Unrelated:

• Add a note to the request_mocker to make sure that mocked results
  are of the correct expected types based on JSON-RPC spec (e.g. hex
  strings instead of ints for numbers, etc.)
• Removed request caching decorator from base providers since they don't implement make_request. This makes typing tighter around the code base as well.
• IPCProvider did not have request caching turned on. This PR turns that on.

Todo:

• Add or update documentation related to these changes. This documentation should detail the underlying mechanism of how (and why) to check certain endpoints against a validation threshold so that users know:

  1. When to reach for caching in the first place
  2. If they reach for caching, clarify internal calls can be made to get the necessary validation data
  3. Know how they can tweak the validation threshold to lower the number of internal calls made (or set it to None to cache any and all requests)

• Add entry to the release notes

• Clean up commit history

Cute Animal Picture

     __      __
    /  \____/  \
   (    o  o    )
    \    ∇     /
     \  \___/  /
      \_______/
        |   |

[kclowes]

Mostly left lazy questions and small things, but looks good otherwise!

[pacrob]

just one q, otherwise lgtm!