Separation of Collection Class into Trait and Interface

[valzargaming]

Description

This PR introduces a modular architecture for the Collection functionality by splitting it into:

1. CollectionTrait: Implements the reusable logic of the Collection class.
2. CollectionInterface: Specifies the contract for collection-related operations.
3. Updated Collection Class: Now leverages CollectionTrait and implements CollectionInterface.

Changes Introduced

1. Addition of CollectionTrait.php:

• Moved shared methods from Collection to a trait for reuse.
• Includes utility functions such as toArray, filter, map, and others.

2. Addition of CollectionInterface.php:

• Declares method signatures for offsetGet, offsetSet, offsetExists, offsetUnset, toArray, and other collection operations.

3. Refactoring of Collection.php:

• Collection now uses the CollectionTrait.
• Implements CollectionInterface.
• Maintains backward compatibility while adhering to the interface contract.

Why This Change?

• Separation of Concerns: Isolates the behavior (trait) and contract (interface), ensuring modularity.
• Improved Testability: With a clearly defined interface, mocking and testing become more straightforward.
• Reusability: The trait can be applied to other classes requiring similar functionality.
• Consistency: Aligns the architecture with best practices for maintainable and extensible codebases.

Impact on Existing Code

• Backward Compatibility: The refactored Collection class maintains the same public API as before.
• Dependencies: Any external code dependent on Collection should continue to work without modification.