Simplify DerivativeWorkflows by Removing Minting Fee Handling

[sebsadface]

Description

Currently, the DerivativeWorkflows contract fetches the minting fee from the core protocol and requires users to transfer this fee to DerivativeWorkflows, which then passes it on to the royalty module. This workaround was necessary because there was no straightforward way for the application to fetch the minting fee directly from the core protocol, preventing users from knowing the exact fee at signing time (see issue #21).

With the recent addition of the predictMintingLicenseFee view function in the core protocol (as outlined in PR #200, the application can now retrieve the latest minting fee in a single function call. This allows users to approve the minting fee directly to the royalty module.

Proposal:

• Remove the logic in DerivativeWorkflows that fetches the minting fee and handles token transfers.
• Assume that the minting fee is already approved to the royalty module when registering derivatives.

Benefits:

• Simplifies the derivative registration workflow.
• Reduces gas costs for derivative registration functions.