fix(registry): remove multicall payable

[saeta-eth]

Using multicall payable could be dangerous. Anyone can call the multicall method on the publish functions and pay only 1 wei (current fee) for all these publishes to the registry. It's not a significant issue since this new version of the CannonRegistry isn't deployed yet and it's only 1 wei, but it's easy to introduce a security hole in the future if it's overlooked.

Ref: Uniswap/v3-periphery#52

[changeset-bot]

⚠️ No Changeset found

Latest commit: bcbd09c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[saeta-eth]

Some thoughts: if the payable modifier is removed, the publish function called by themulticall won't work, we may need to re-think the fee or multicall implementation.