Collision System Collider enabled checks added.

[SoloByte]

Refactor: CollisionHandler Query-,Cast-, and IntersectSpace functions now correctly check if collider used is enabled. Refactor: SpatialHash certain functions that work with colliders are now correctly checking if the collider is enabled.

[Copilot]

Pull Request Overview

This PR ensures that disabled colliders are skipped in spatial hash operations and collision handler queries.

• Added early Enabled checks in SpatialHash methods
• Introduced Enabled guards and updated XML docs in CollisionHandler queries

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.

File	Description
ShapeEngine/Geometry/CollisionSystem/SpatialHash.cs	Early-return if collider.Enabled is false in registration, candidate and add methods
ShapeEngine/Geometry/CollisionSystem/CollisionHandler.cs	Guards against disabled colliders in IntersectSpace, CastSpace and updated parameter docs

Comments suppressed due to low confidence (2)

ShapeEngine/Geometry/CollisionSystem/CollisionHandler.cs:650

• [nitpick] Replace the exclamation mark with a period to maintain a formal tone in XML documentation.

    /// <param name="collider">The collider to test for intersections. The collider needs to be enabled!</param>

ShapeEngine/Geometry/CollisionSystem/CollisionHandler.cs:658

• Add unit tests to verify that IntersectSpace returns null when collider.Enabled is false.

        if(!collider.Enabled) return null;