feat: add RPC methods described in (revised) EIP-7715

[jeffsmale90]

Adds methods wallet_requestExecutionPermissions and wallet_revokeExecutionPermission, as defined in this revision of the EIP-7715 specification ethereum/ERCs#1098.

This supports Readable Permissions project, and is related to the following PRs:

• Support calling wallet_requestExecutionPermissions directly on the wallet api delegation-toolkit#60
• feat: add wallet_requestExecutionPermissions method metamask-extension#35193

Note: workflows are failing due to existing problems, fixed by #397

[jiexi]

functionally LGTM. I have some concerns regarding spec about if isAdjustmentAllowed should even be included as it ultimately is a proxy for something optional and if something is not strictly required for execution then IMO it should not be included in the request by the dapp

Please ping for re-approval if you feel that my nit above is fair

[adonesky1]

I believe you'll need to pass end in as a param as well for the JSON RPC Engine to handle this gracefully

Suggested change

	res.result = await processRequestExecutionPermissions(params, req);
	}
	res.result = await processRequestExecutionPermissions(params, req);
	return end()
	}

[adonesky1]

I guess they aren't doing this in the 5792 methods you used as a model. Need to figure out why that's ok 🤔

[jeffsmale90]

From @metamask/json-rpc-engine - createAsyncMiddleware:

* Async middleware have no "end" function. Instead, they "end" if they return
* without calling "next". Rather than passing in explicit return handlers,
* async middleware can simply await "next", and perform operations on the
* response object when execution resumes.

The async middleware function accepts a next parameter, but no end parameter. 😅

[mj-kiwi]

Should these two type names be singular to stay consistent with the singular form of wallet_revokeExecutionPermission?

[jeffsmale90]

You are absolutely correct!