feat: specify validation-associated exec hooks as permission hooks

standard/ERCs/erc-6900.md

@@ -563,7 +563,7 @@ For all non-view functions within `IModularAccount` except `executeWithAuthoriza
 
 If the caller is not the EntryPoint or the account, the account MUST check access control for direct call validation.
 
-Prior to running the target function, the modular account MUST run all pre execution hooks that apply for the current function call. Pre execution hooks apply if they have been installed to the currently running function selector, or if they are installed to the validation function that was used for the current execution. Pre execution hooks MUST run validation-associated hooks first, in the order they were installed, then selector-associated hooks second, in the order they were installed.
+Prior to running the target function, the modular account MUST run all pre execution hooks that apply for the current function call. Pre execution hooks apply if they have been installed to the currently running function selector, or if they are installed as a permission hook to the validation function that was used for the current execution. Pre execution hooks MUST run validation-associated hooks first, in the order they were installed, then selector-associated hooks second, in the order they were installed.
 
 Next, the modular account MUST run the target function, either an account native function or a module-defined execution function.