feat(briefcase): add deployers for permissioned-pool contracts

[SocksNFlops]

Pull Request

Description

Adds the deploy infrastructure for the Permissioned Pools stack — new deployer libraries, task_template.json entries, and Deploy-all.s.sol wiring for:

Contract	Source	Notes
PermissionsAdapterFactory	v4-periphery (hooks/permissionedPools/)	runs=44444444, via_ir=true
PermissionedPositionManager	v4-periphery (hooks/permissionedPools/)	runs=500 (EIP-170 fit at 23,198 bytes)
PermissionedHooks	v4-hooks-public (permissioned-pools/)	runs=44444444, via_ir=false; salt-mined
UniversalRouter (V2.2.0)	universal-router	runs=1; adds permissionsAdapterFactory to RouterParameters (11th field)

Also adds Uniswap/v4-hooks-public as a new submodule.

Fixes # ECO-190

Upstream PRs landed before this

• Permissioned Pools v4-periphery#476 (merged — Permissioned Pools + hook migration out)
• feat(permissioned-pools): migrate PermissionedHooks from v4-periphery v4-hooks-public#20 (merged — Permissioned Hooks)
• refactor(v4-swap-router): inherit PermissionedV4Router from v4-periphery universal-router#476 (open — permissionsAdapterFactory in RouterParameters)

⚠️ On the diff size (61 files)

Only ~15 files are perm-pool specific. The remaining ~45 are src/briefcase/protocols/** regeneration catch-up: main's committed protocols/ had drifted from its own pinned submodule SHAs (UR BytesLib, Commands, UniswapX struct renames, etc.). Running create_briefcase.sh against the current pins materializes the catch-up. No upstream SHAs other than v4-hooks-public are bumped by this PR.

Sanity check from a clean main checkout: run ./script/util/create_briefcase.sh without any of this PR's changes — you'll see the same ~45 files of drift.

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration.

Checklist:

Before deployment

• 100% test and branch coverage
• check slither for severe issues
• fuzz and invariant tests (when applicable)
• formal verification (when applicable)
• deployment or upgrade scripts ready

After deployment

• transfer ownership after deployments (when applicable)
• complete upgrade (when applicable)
• generate deployment/upgrade log files

---

Considerations

• I have followed the contributing guidelines.
• My code follows the style guidelines of this project and I have run forge fmt and prettier to ensure the code style is valid
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

Additional context

Add any other context about the pull request here.