Gas data and metadata did not even consistent error behavior across
different code path. Particularly the difference between dev inspect,
dry run and execution do not help developers or ptb builders.
Making the behavior consistent across different code path

Locally and changes to the fuzzer/proptest framework and tests are
coming in a next PR as they are pretty involving

---

Check each box that your changes affect. If none of the boxes relate to
your changes, release notes aren't required.

For each box you select, include information after the relevant heading
that describes the impact of your changes that a user might notice and
any actions they must take to implement updates.

- [x] Protocol: in version 111 error from dev inspect, dry run and
execution are more consistent and the same for transaction data checks
- [ ] Nodes (Validators and Full nodes):
- [ ] gRPC:
- [ ] JSON-RPC:
- [ ] GraphQL:
- [ ] CLI:
- [ ] Rust SDK:
- [ ] Indexing Framework: