Support calling wallet_requestExecutionPermissions directly on the wallet api

[jeffsmale90]

📝 Description

It is now possible to configure MetaMask extension to forward calls to wallet_requestExecutionPermissions calls to the wallet API to the permissions kernel snap. This change adds support for this, while continuing to maintain support for calling the snap directly.

The experimental EIP-7715 functionality in the Delegation Toolkit now calls wallet_requestExecutionPermissions on the wallet API directly. There is no longer support for calling the snap directly.

🔄 What Changed?

When configuring the erc7715ProviderActions, a caller may provide an Erc7715ProviderConfig that conforms to the following definition:

type Erc7715ProviderConfig = {
useWalletMethod: boolean;
snapIds:? {
kernelSnapId?: string;
providerSnapId?: string;
}
};

If useWalletMethod is true, any snap configuration is ignored, and the request is made directly to wallet_requestExecutionPermissions on the wallet's injected provider.

If useWalletMethod is false, the request is made to the kernel snap.

If no snap ids are specified, the default values npm:@metamask/permissions-kernel-snap and npm:@metamask/gator-permissions-snap are used.

Support for calling the snaps directly will likely be removed at some stage in the future.

When configuring the erc7715ProviderActions a caller no longer must provide snapId configuration:

~const client = createClient({
  transport: custom(window.ethereum)
}).extend(erc7715ProviderActions());~

This will route all requests to the experimental EIP-7715 methods to the wallet_requestExecutionPermissions on the injected ethereum API.

🧪 How to Test?

Install in the Snap-7715 site, and configure the Eip7715 client with { useWalletMethod: true } no configuration. Ensure that Flask is installed with MetaMask/metamask-extension#35193 installed. The site should function as normal.

⚠️ Breaking Changes

List any breaking changes:

• No breaking changes
• Breaking changes (describe below):

Changes the configuration parameters of Erc7715 actions constructor, to nest the snapIds into a child property.
No configuration parameters are required when configuring the Erc7715 actions.

📋 Checklist

Check off completed items:

• Code follows the project's coding standards
• Self-review completed
• Documentation updated (if needed)
• Tests added/updated
• Changelog updated (if needed)
• All CI checks pass

🔗 Related Issues

Link to related issues:
Closes #
Related to #

📚 Additional Notes

Any additional information, concerns, or context: