Fix regressions archetype table separation introduced

[waynemwashuma]

Objective

Addresses critical logical and performance regressions and soundness issues in the ECS world.

• The regression was introduced by Separate data tables and archetypes #243 and was fixed by Resolve duplicate component entries #159 previously.

Solution

• Fixed Archetype Resolution: Deduplicated type IDs are used to create creating new archetypes, preventing duplicate component types from causing incorrect archetype matching.
• Optimized Component Insertion: When inserting components into an existing entity, the system now checks if the operation can be performed within the same table instead of always moving to a new table. This eliminates unnecessary data movement when the table structure doesn't change.

Showcase

The improvements are most noticeable in scenarios with frequent component additions and dublicate components:

Migration Guide

No breaking changes were introduced.

Checklist

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.