Consider more restrictive schemas for EVM base types

[cygnusv]

I was thinking about this some more. Perhaps we need to separate this schema into two parts.

1. What is allowed for blockchain RPC / smart contract calls
2. What is generally allowed

The original goal of the paramSchema on L9 was 2), but we are now limiting it to 1).

Solidity doesn't have floating point numbers, so limiting it to z.number().int() is fine. However, a JsonApiCondition can require floating point numbers. For example, the paramOrContextParamSchema is used for the value used for the returnValueTest () - and for a JSON API, checking a floating point number is perfectly fine, but now it won't be; typified by the fact that I saw you had to modify the floating point test.

Originally posted by @derekpierre in #598 (comment)