Add ability for L1 to claim L2 royalties

[tomwade]

This adds a call to the L1 Bridge so that contracts that support the IERC2981 interface can claim royalties to a specific L2 recipient.

One short fall of this implementation is that we only look at tokenId 0 to validate the msg.sender. This means that anyone with access to royalties of the zero token could claim royalties across the whole project. I don't believe there are many instances in which this would be worrying for an NFT project though.

Question:

• Does this cover enough royalty implementations? This adopts the standard, but I don't know if there are any mainstream projects that would need a caveat (like Punks for transfers)
• Sorry there are a number of other QoL updates in this PR as well, I should have split those out