Come up with uniform versioning scheme for methods

There are several possibilities here:
1) add version parameter to the end - I think this is mostly backward compatible, if it isn't added just assume v1
2) add version parameter at beginning - not backwards compatible, benefit is ???
3) all methods accept 1 object with version as top-level value then args - ???
4) add new method for backwards incompatible changes - similar to engine api
5) new method which says which version the api is and move the entire api forward with new version updates
6) ??? probably a lot more possibilities that haven't been thought through

_Originally posted by @lightclient in https://github.com/ethereum/execution-apis/pull/383#discussion_r1198082013_