Feat: Initial attemptBatchMint functionality

[CruzMolina]

• refactor: expand PerpetualMintInternal _requestRandomWords to pass PerpetualMint Storage.Layout as a parameter
• feat: define CollectionNotActive custom error in IPerpetualMintInternal
• feat: define InvalidNumberOfMints custom error in IPerpetualMintInternal
• refactor: PerpetualMintInternal _attemptMint to _attemptBatchMint for supporting multiple mint attempts per tx
• refactor: IPerpetualMint attemptMint -> attemptBatchMint for supporting multiple mint attempts per tx
• refactor: PerpetualMint attemptMint -> attemptBatchMint for supporting multiple mint attempts per tx
• build: update PerpetualMintHelper facet cut selector, attemptMint -> attemptBatchMint
• feat: initial PerpetualMintInternal _setMintFeeBP fn
• feat: define setMintFeeBP fn in IPerpetualMint
• feat: add setMintFeeBP fn to PerpetualMint
• build: add setMintFeeBP fn selector to PerpetualMintHelper for diamondCut
• build: set VRF subscriptionId as a test constant in PerpetualMintTest
• build: rm redundant VRF_COORDINATOR address casting
• build: fix StorageRead _protocolFees storage slot calculation
• build: fix StorageRead _mintFeeBP storage slot calculation
• build: add initial IVRFCoordinatorV2Events test interface
• build: initial PerpetualMint attemptBatchMint behavior tests

[CruzMolina]

I doubt there will be enough gas to mint 100x, so it may be worthwhile at some point to check what the max mint number is based on that constraint versus the Chainlink VRF max words constraint.

That's my plan when reworking the mint fulfillment/resolution side of things. Will be adding test cases to see what we can expect as a real constraint.