Add EIP: Auditable JSON-RPC API Specification

[blockjoe]

I'm starting the process by opening up the PR for the draft here.

I'm happy to open up the discussion topic on Ethereum Magicians, but I guess I need to wait for my account to clear the new user bar.

Currently, the reference implementation and test cases I'm happy to move those into a corresponding assets directory either before or after the number assignment. Additionally, I do have another supporting PDF artifact to be placed in said assets directory. I just wasn't sure about the process of creating a directory called eip-draft_auitable_rpc or if I should wait for a number assignment.

[eth-bot]

File EIPS/eip-draft_auditable_rpc.md

Requires 1 more reviewers from @axic, @lightclient, @SamWilsn

[abcoathup]

@blockjoe API standards should be directed to https://github.com/ethereum/execution-apis nowadays

[blockjoe]

Hey @abcoathup given your feedback I'm assuming the main copy on the EIP site needs to be updated to reflect this, as it still communicates the Interface track for API standards.

That being said, while I'm happy to submit the reference and test cases as updates to the existing OpenRPC specification, I've included a disclosure in the directory assets/eip-draft_auditable_rpc in this PR as to why I feel keeping the visibility of these changes in the previously mentioned process should be strongly considered.

Again, would love to discuss further on Magicians, but still cannot create any posts to do so.

[github-actions]

The commit f036de9 (as a parent of ad2bebd) contains errors.
Please inspect the Run Summary for details.

[lightclient]

Closing this as RPC changes should be sent to ethereum/execution-apis