fix: rename permit2ApproveZero to permit2Approve

[jeffsmale90]

📝 Description

The terms property for ApprovalRevocationEnforcer, and data property for token-approval-revocation ERC-7715 permission type was incorrectly specified as permit2ApproveZero. This PR corrects that to permit2Approve.

🔄 What Changed?

List the specific changes made:

• TokenApprovalRevocationPermission in @metamask/7715-permission-types updated
• ApprovalRevocationTerms updated in core terms encoder / decoder
• ERC-7715 wallet actions data mapping updated

🚀 Why?

Explain the motivation behind these changes:

Corrects inconsistency in public facing APIs.

🧪 How to Test?

Describe how to test these changes:

• Manual testing steps:

• Automated tests added/updated
• All existing tests pass

⚠️ Breaking Changes

List any breaking changes:

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

📋 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:

---

Note

Medium Risk
Renames a public-facing field in ERC-7715 permission and approval-revocation terms; consumers sending/expecting permit2ApproveZero will break until updated. Logic remains the same but the change touches encoding/decoding and RPC mapping surfaces.

Overview
Fixes an API naming mismatch by renaming the Permit2 revocation flag from permit2ApproveZero to permit2Approve across the ERC-7715 token-approval-revocation permission type and ApprovalRevocationEnforcer terms.

Updates the core bitmask encoder/decoder, smart-accounts-kit RPC mapping, and unit/e2e tests and changelogs to use the corrected field name.

^{Reviewed by Cursor Bugbot for commit b273be2. Bugbot is set up for automated code reviews on this repo. Configure here.}

[mj-kiwi]

LGTM