When using React Compiler or other tools that freeze objects,
`route.params` can become non-extensible. The `Object.defineProperty`
call to set `CONSUMED_PARAMS` then throws:
`TypeError: Cannot add new property 'CONSUMED_PARAMS'`

Add an `Object.isExtensible()` check before attempting to define the
property, matching the pattern suggested in react-navigation#13033.

Fixes react-navigation#13033

…ARAMS

Replace the symbol-based mutation approach with a module-level WeakSet
to track consumed params. This avoids mutating route.params entirely,
which fixes compatibility with React Compiler and other tools that
freeze objects.

The WeakSet approach:
- Does not mutate route.params (works with frozen/sealed objects)
- Automatically cleans up when params objects are GC'd (no memory leaks)
- Preserves the same semantics: params are marked as consumed after
  being processed by a nested navigator

…tracking

Instead of a global WeakSet, store consumed params state per navigator
instance using a React context provided by SceneView.

- Add ConsumedParamsContext with WeakRef<object> | null state
- SceneView provides the context, scoping tracking to each navigator
- useNavigationBuilder consumes the context to check/set consumed params
- No mutation of route.params (works with frozen objects / React Compiler)
- No shared state between navigator instances

Fixes react-navigation#13033