feat: integrate ERC-8001 multi-party coordination via hook pattern

[KBryan]

Add ERC-8001 standard-compliant multi-party coordination framework integrated with ERC-8183 hooks. This implementation follows the authors' preferred hook pattern over the evaluator pattern. Changes:

• Add ERC8001.sol base contract with full EIP-712, ERC-1271, and ERC-5267 support for multi-party coordination
• Add ERC8001CoordinationHook.sol (Profile B) for optional per-job coordination of complete/reject actions
• Remove MultiPartyEvaluator.sol in favor of hook pattern
• Add comprehensive Foundry test suite (ERC8001.t.sol, ERC8001CoordinationHook.t.sol)
• Update documentation (README.md, hook-profiles.md) with new hook example and testing instructions Features:
• Standard-compliant ERC-8001 implementation
• EIP-712 signature verification (ECDSA 65/64-byte, ERC-1271)
• Strict participant canonicalization (sorted unique)
• Monotonic nonce enforcement per agent
• Optional per-job coordination (backward compatible)
• Gas-efficient: minimal hook state, complex logic in base contract Breaking Changes:
• Remove contracts/examples/MultiPartyEvaluator.sol (replaced by hook pattern)

[psmiratisu]

Thanks for the PR! Multi-party coordination is valuable for complex jobs that need multiple providers (e.g., 5 reviewers, 3 validators working together).

Architecture question:
The current implementation hardcodes to ERC-8001 (your proposed standard). This creates a standard-to-standard dependency. Wonder if it would be better to have an approach that extract IMultiPartyCoordination interface and have ERC 8004 to be the reference implementation ?

interface IMultiPartyCoordination {
    function addProvider(bytes32 jobId, address provider) external;
    function removeProvider(bytes32 jobId, address provider) external;
    function getProviders(bytes32 jobId) external view returns (address[] memory);
    function isValidProviderSet(bytes32 jobId) external view returns (bool);
    function distributePayment(bytes32 jobId, uint256[] calldata shares) external;
}

Would you be open to this refactor? Happy to collaborate on interface design.

[KBryan]

@psmiratisu noted, I made some edits to my PR. Please review at your earliest convenience. Also looking into collaborating on interface design.

[KBryan]

@psmiratisu, just checking in to see if you have had a chance to go over my latest revisions. also wondering if you are planning to have erc-8183 breakout sessions

[psmiratisu]

@KBryan yes, we will have breakout in maybe 2 weeks from now!!

for this PR tho, there is valuable work in here, but I do not think this can merge in the current bundled form. It is carrying too much at once for hook-contracts. The path I would suggest is to split out the smallest standalone coordination hook first, split any multi-provider payment hook separately, keep the full ERC-8001 implementation and broader coordination infrastructure out of this repo path, and keep the repo examples depending on interfaces rather than bundling the entire system into one PR. If you want to keep going on this, I am happy to review the smaller split PRs. I do not think the full bundled version should land as-is. What do you think?