Simplify Signature Requirements for SPG Functions

[sebsadface]

Description

Currently, registerIpAndAttachPILTerms, registerIpAndMakeDerivative, andregisterIpAndMakeDerivativeWithLicenseTokens in the SPG requires multiple signatures to set permission, which adds complexity for developments. To improve developer experience, we can modify this function to require only a single signature by utilizing the setBatchPermissions method in core protocol's AccessController contract.

[sebsadface]

As we transition from the set permission model to using executeWithSig from IPAccount for security reasons (refer to #121), further simplifying the signature requirements is not currently feasible. Each executeWithSig call requires a unique signature, which limits our ability to simplify this process.