1. 1. Ticket

Add `assumes_stable_collection_uuid` tag to `near_memory_limit.js`

1. 1. What this PR does

Adds the `assumes_stable_collection_uuid` tag to `jstests/core/query/geo/near_memory_limit.js`, causing it to be excluded from the `sharding_jscore_passthrough_with_balancer` suite (and any other suite that performs background `moveCollection` operations).

1. 1. Why

`near_memory_limit.js` runs a `$geoNear` aggregate over 10,000 documents, requiring multiple `getMore` calls to exhaust the cursor. In `sharding_jscore_passthrough_with_balancer`, the suite uses `random_migrations: true` which calls `moveCollection` in the background. When `moveCollection` commits, it drops and recreates the collection with a new UUID; any in-flight query using the auto-yielding policy then receives `QueryPlanKilled` (code 175) on the next yield-restore cycle.

The passthrough's retry logic does retry `QueryPlanKilled`, but the large result set means the query takes long enough that migrations keep killing it on every attempt, ultimately timing out the `assert.soon` in the override after 600 seconds. This is the same root cause tracked in SERVER-88275.

The identical fix was applied to `geo_circle_spilling.js` in SERVER-113548, and to an earlier batch of tests in SERVER-88882.

1. 1. Reviewer reading guide

The entire diff is one line: adding `assumes_stable_collection_uuid` to the `@tags` block in `near_memory_limit.js`. No logic changes.

1. 1. Followups

SERVER-88275 tracks the underlying issue (making `moveCollection` not kill in-flight queries). Until that is fixed, tests with long-running cursors that are sensitive to UUID changes need this tag.