feat: enable token template upgrades through TokenizerModule

[sebsadface]

Description

This PR adds the ability to upgrade whitelisted token template implementations in the TokenizerModule. The enhancement enables controlled upgrades of token implementations while maintaining system security through proper access controls.

Changes

• Added upgradeWhitelistedTokenTemplate function to the TokenizerModule and its interface
• Updated the Errors library with a new error for zero token implementation validation
• Transferred ownership of the ownableERC20Beacon to the TokenizerModule
• Added tests to verify upgrade functionality works correctly

Security Considerations

• Function is restricted to be called only by the upgrader admin through the restricted modifier
• Multiple validation checks ensure that:
  • Token template address is not zero
  • New implementation address is not zero
  • Token template is whitelisted

Testing

Added two test cases:

1. Successfully upgrading a whitelisted token template
2. Verifying reversion when attempting to upgrade a non-whitelisted template

[kingster-will]

Why we need this feature?

[sebsadface]

Why we need this feature?

We need this to allow upgrading the token template directly from the Tokenizer module, and to integrate with our Access Manager. This is similar to how we currently handle upgrades for IPRoyaltyVault (via RoyaltyModule), IPAccount (via IIPAssetRegistry), and SPGNFT (via RegistrationWorkflows).

Otherwise, we'd have to upgrade the OwnableERC20 template by directly calling the Upgradeable Beacon, which requires action by the beacon owner (currently the deployer). That’s less flexible and inconsistent with our other upgrade methods.

[kingster-will]

I see.
I meant, why do we need this PR now? Is there a known use case that requires this feature, or do we consider it just a missing feature gap in the current version?

[sebsadface]

I see. I meant, why do we need this PR now? Is there a known use case that requires this feature, or do we consider it just a missing feature gap in the current version?

Got it! There’s no known use case currently requiring this feature; we consider it as a feature gap in the existing version. I noticed this issue while working on #178 where I’m improving the upgrade scripts