Move License Template compatibility check to individual LicenseTemplates

[jdubpark]

Currently, there's a global restriction in allowing only one license template per IP.

For example, if IP attaches PIL licenses, it can't attach licenses from other templates.

protocol-core-v1/contracts/registries/LicenseRegistry.sol

Lines 209 to 211 in 5d91e7a

	if ($.licenseTemplates[ipId] != address(0) && $.licenseTemplates[ipId] != licenseTemplate) {
	revert Errors.LicenseRegistry__UnmatchedLicenseTemplate(ipId, $.licenseTemplates[ipId], licenseTemplate);
	}

This restriction might be very restrictive for some license templates, such as when a user wants to attach MIT licenses and some other licenses from different license templates.

Hence, we should move this check to be within each license template.

[Ramarti]

I think for this release we are safer without this feature.

We would have to be able to have inter-template compatibility checks, with common values that mean the same for every template.

I think the minimum variables that could be reused across templates and help reduce significant compatibility issues are:

• commercialUse
• derivativesAllowed

An alternative is to allow templates to say if they are compatible with others, but that puts a lot of trust on the templates, especially if we want too open template registration. One template would have to trust the other template did not alter the Licensing terms after claiming compatibility, potentially rugging the user.

In beta, the solution was storing LicensePolicy data in LicensingModule and not allowing modifications from the templates (then frameworks). That way data is stored in the protocol, and templates/users can make decisions using a License without fear of being rugged by the LicenseTemplate.

We would need to find a way of doing this without complicating the DX with encoding, or doing very simple encoding.