fix(trash-cleanup): never clean grids hosting worldloaders

[Kronyxxx]

Summary

Adds a safety guard to trash cleanup so infrastructure grids that host world loaders are never deleted by distance-based cleanup.

Problem

Trash cleanup currently protects loader-adjacent grids indirectly via protection zones calculated from world loader positions. If those assumptions drift or a loader edge case occurs, a critical loader-hosting grid can still become cleanup-eligible.

Solution

Add a direct guard in ShouldProtectGrid():

• If a grid has WorldLoaderComponent, treat it as protected and skip cleanup.

Files Changed

• Content.Server/Trash/TrashCleanupSystem.cs

Behavior Impact

• Loader-hosting grids are now always excluded from trash cleanup.
• No gameplay/system behavior changes outside cleanup eligibility.

Risk

Low.

• Change is narrowly scoped to one protection predicate.
• Only affects grids explicitly carrying WorldLoaderComponent.

Validation

• Verified diagnostics: no errors in modified file.
• Confirmed change is limited to cleanup protection logic.

Related

• Follow-up to fix(colcomm): prevent colcomm grid/shuttle cleanup and self-heal stale colcomm state #1658.

[ShadesMars]

If doing this way, delete CleanupProtectedGridComponent as its not usefull.

Worldloader can also be disabled in a variable, so lets not have two comp that does the same.

[Kronyxxx]

still a draft lol yeah