Modularization of CDT for Enhanced Developer Flexibility

[bhazzard]

User Story:
As a blockchain developer, I want to have the ability to selectively integrate specific libraries with the features I need to develop my smart contracts, so that I can avoid upgrading for features I don't need.

Problem:
Currently, the developer experience with the Contract Development Toolkit (CDT) requires updating to the latest version whenever new features are released. This is not always necessary or desired, as many developers may not require the newly added features. This process places undue pressure on all developers to upgrade, even when it's irrelevant to their needs.

Proposal:
We should evolve from the current "kitchen sink" CDT to a more modular system. We can do this by creating smaller, independent libraries for specific functionalities.

Examples of candidates for libraries:

• BLS
• BN256
• Multi Index Tables
• Serialization
• Crypto

Benefits:
These libraries would be separate from the main CDT release and would update independently, allowing developers to pick and choose what they need and ensuring compatibility across multiple versions of CDT.

Requirements:

1. Modular: Develop independent libraries for specific functionalities that are currently bundled in CDT.
2. Compatible: Ensure that these libraries are compatible with CDT.
3. Decoupled: Ensure that these CDT upgrades don't require upgrading Library versions and vice versa.
4. Release Cadence: Establish a distinct release schedule for these libraries, independent of the CDT release cycle.
5. Documentation: Update documentation so developers know which libraries to use, where to get them, and how to use them.

Acceptance Criteria:

1. Selective Integration: Developers should be able to integrate only the libraries they need for their project.
2. Backward Compatibility: The new libraries must be compatible with at least the previous two major releases of CDT.
3. Independent Functionality: Each library should function independently without requiring a full CDT upgrade.
4. Documentation Clarity: The documentation should clearly explain how to integrate and use each library.