CONTRACTS: Add Token Upgrade Mechanism

[truthixify]

Description
Implement upgrade functionality allowing tokens to be upgraded to new versions with enhanced features while preserving ownership and history.

Files to Modify

• contracts/manage_hub/src/upgrade.rs - Create upgrade module
• contracts/manage_hub/src/types.rs - Add upgrade structures
• contracts/manage_hub/src/migration.rs - Add migration helpers
• contracts/manage_hub/src/lib.rs - Add upgrade endpoints

Key Changes Required

• Upgrade Function - Upgrade tokens to new versions
• Version Tracking - Track token versions and upgrade history
• Migration Logic - Migrate data from old to new versions
• Backward Compatibility - Maintain compatibility with old versions
• Upgrade Authorization - Control who can trigger upgrades
• Rollback Mechanism - Add ability to rollback failed upgrades

Acceptance Criteria

• Implement upgrade_token function with version parameter
• Add version tracking to token structure
• Create migration functions for data transformation
• Emit TokenUpgraded events
• Add get_token_version query function
• Support batch upgrades for multiple tokens
• Implement upgrade authorization checks
• Add upgrade history tracking

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 150 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave