Extract MintPolicyManager into its own component

[onurinanc]

MintPolicyManager is currently tied into AuthControlled and OwnerControlled. We would like to consider decoupling the policy manager into its own component, so policy selection and policy enforcement are not implicitly bundled together.

• The idea is originally here by @bobbinth: Flexible Minting Policies for Token Standards #2559 (comment)
• Supporting idea to consider this as a part of Role-Based Access Control: Flexible Minting Policies for Token Standards #2559 (comment)
• Follow-up PR to: Flexible Minting Policies for Token Standards #2559
• Related Issue: Make MintPolicyManager into a stand-alone component OpenZeppelin/miden-confidential-contracts#84

[onurinanc]

Additionally, move the static variables such as MINT_POLICY_AUTH_CONTROLLED_LIBRARY and MINT_POLICY_OWNER_CONTROLLED_LIBRARY into relevant modules similar to here: #2603 (comment)

[PhilippGackstatter]

Something else to look into is whether we still need:

• BurnOwnerControlledConfig and BurnPolicyAuthority
• MintOwnerControlledConfig and MintPolicyAuthority

I think having both of these may be a symptom of not having a single policy manager component, but have these integrated into each concrete policy component (*AuthControlled or *OwnerControlled). But I could be missing something.

[onurinanc]

Thank you for the comment @PhilippGackstatter I'll be addressing this after role-based access control as I specified here: #2664 (comment)