Consider decoupling the VestingWalletExecutorConfidential from VestingWallet

[Amxx]

The executor logic, is "just" about having a priviledge account (the executor) that can perform call from the contract. While this is used in the context of the VestingWallet, its an independant feature.

I would implement it independantly of the VestingWallet (no import/no inheritance). The two can then be combined

[Amxx]

Note that you may be able to reuse Account logic from @openzeppelin/contracts

import {ERC7821} from "@openzeppelin/contracts/account/extensions/draft-ERC7821.sol";
import {StorageSlot} from "@openzeppelin/contracts/utils/StorageSlot.sol";

contract WithExecutor is ERC7821 {
    using StorageSlot for bytes32;

    // keccak256(abi.encode(uint256(keccak256("openzeppelin.storage.WithExecutorStorage")) - 1)) & ~bytes32(uint256(0xff))
    // solhint-disable-next-line const-name-snakecase
    bytes32 private constant WithExecutorStorageLocation = ...;

    // solhint-disable-next-line func-name-mixedcase
    function __WithExecutor_init(address executor_) internal onlyInitializing {
        WithExecutorStorageLocation.getAddressSlot().value = executor_;
    }

    /// @dev Trusted address that is able to execute arbitrary calls from the vesting wallet via {call}.
    function executor() public view virtual returns (address) {
        return WithExecutorStorageLocation.getAddressSlot().value;
    }

    function _erc7821AuthorizedExecutor(
        address caller,
        bytes32 mode,
        bytes calldata executionData
    ) internal view virtual override returns (bool) {
        return caller == executor() || super._erc7821AuthorizedExecutor(caller, mode, executionData);
    }
}

[arr00]

Resolved in #104