[Sensor] Fix ray caster path matching regressions

[StafaH]

Description

This PR fixes the two remaining ray-caster path-matching failures:

1. The ray-caster camera tutorial counted four sensors for two camera prims because /World/Origin_.*/CameraSensor allowed .* to cross path separators under whole-path regular-expression matching.
2. Legacy Newton multi-mesh ray casters could fail to associate tracked-target sites when registration used a regular-expression path but initialization resolved it to concrete prim paths.

The stale post-reset Newton sensor result reported in #7236 is now fixed at the sensor state boundary by #7523, which this branch inherits from develop. The earlier environment-loop synchronization workaround and its tests/changelog fragments have therefore been removed from this PR.

Changes

• Restrict the tutorial environment wildcard to one path segment with /World/Origin_[^/]+/CameraSensor.
• Associate legacy Newton tracked-target site labels by configuration order instead of path-expression strings.
• Remove the obsolete --enable_cameras argument from the tutorial smoke case.
• Add regression coverage for regular-expression target resolution.

Fixes #6572

Related: #7236, resolved by #7523.

Type of change

• Bug fix (non-breaking change which fixes an issue)

Release backport

• Backport this pull request to the active release branch after it merges into develop

Screenshots

Not applicable.

Validation

• uv run python -m pytest source/isaaclab_newton/test/sensors/test_newton_raycast_sensor.py -vv (18 passed, including the [Newton] Refresh FK before ray-cast sensor reads #7523 FK regressions in eager and CUDA-graph modes)
• uv run python -m pytest source/isaaclab/test/app/test_standalone_scripts.py::test_commands_respect_script_launcher_capabilities -vv (1 passed)
• Verified the ad-hoc tracked-target regression fails with the old string-key association and passes with this fix in eager and CUDA-graph modes.
• Verified the exact clone-plan topology from [Bug][Newton] MultiMeshRayCaster tracked targets: registered body_pattern (clone-dest glob) never matches prototype body labels #6572 passes on the merged branch in eager and CUDA-graph modes.
• ISAACLAB_CHANGELOG_BASE_REF=upstream-develop uv run isaaclab -f

The full standalone Newton multi-object demo smoke could not launch in this checkout because the newly merged installer guard rejects combining the downloaded Isaac Sim package with the active Python virtual environment; it exited before application startup.

Checklist

• I have read and understood the contribution guidelines
• I have run the pre-commit checks
• I have made corresponding changes to the tutorial and smoke configuration
• My changes generate no new warnings
• I have added tests that prove the remaining fix is effective
• I have added changelog fragments for the touched source packages
• My name already exists in CONTRIBUTORS.md

[isaaclab-review-bot]

Isaac Lab Review Bot

Reviewed the bounded tutorial camera regex, smoke-command cleanup, and legacy Newton tracked-target association change. The patch consistently updates the affected producer/consumer paths and adds focused regression coverage for resolving a configured regex to a concrete tracked target.

• Design and architecture: The Newton-specific fix remains confined to _LegacyNewtonRayCasterMixin. Associating registered site-label groups with tracked targets in configuration order aligns with mesh-view initialization and the existing ordered traversal in _update_mesh_transforms; the main tradeoff is reliance on that initialization order rather than expression-key identity.
• API: No public API is added, removed, or renamed. The smoke override now matches the tutorial launcher capabilities, and the Newton package includes an appropriate user-visible changelog fragment.
• Implementation: The tracked-target index is reset before every warp-mesh initialization, preventing stale state on reinitialization. The new regression test exercises the concrete-path-versus-regex case addressed by the fix. A residual maintenance dependency remains: tracked views must continue to be created exactly once per tracked target and in configuration order.

No blocking issues. No inline issue met the actionable-evidence threshold; the assessment above records the review feedback.

Automated review; human maintainers own approval decisions.

[greptile-apps]

Greptile Summary

This PR fixes whole-path regular-expression handling for ray-caster cameras and legacy Newton tracked targets.

• Bounds the tutorial environment wildcard to one path segment.
• Associates tracked-target site labels with target configurations by their stable initialization order.
• Removes an obsolete camera-launch argument from the tutorial smoke case.
• Adds regression coverage for an ad hoc regex target resolving to a concrete Newton path.

Confidence Score: 5/5

The PR appears safe to merge, with the changed path matching and tracked-target association consistent with the relevant initialization and launcher contracts.

The ordered label registration and consumption paths use the same stable target configuration order, reinitialization resets the cursor, the bounded regex matches the intended camera prims, and the Warp-based tutorial does not require RTX camera enablement.

Important Files Changed

Filename	Overview
source/isaaclab_newton/isaaclab_newton/sensors/ray_caster/legacy_ray_caster.py	Replaces brittle expression-keyed site-label lookup with ordered association and resets that association before every mesh initialization.
source/isaaclab_newton/test/sensors/test_newton_raycast_sensor.py	Adds focused regression coverage proving that a regex-registered tracked target initializes and produces the expected sensor batch.
scripts/tutorials/04_sensors/run_ray_caster_camera.py	Restricts the environment wildcard to a single path segment so exactly the intended camera prims are selected.
source/isaaclab/test/app/standalone_script_cases.py	Stops passing an unnecessary RTX camera-enablement argument to the Warp ray-caster camera tutorial.
source/isaaclab/test/app/test_standalone_scripts.py	Updates launcher capability coverage to assert that the obsolete camera argument is absent.

_{Reviews (1): Last reviewed commit: "Fix ray caster path matching regressions" | Re-trigger Greptile}

[kellyguo11]

should this also be guarded with len(reset_env_ids) > 0? would this impact perf on the environments?

[StafaH]

This is now removed

[ooctipus]

Changes the stepping logic might be a bit concerning, I think the root issue is that raycast sensor is not following the read access lazy update that all other assets and sensors are following.

#7523 might be an alternative root fix

[StafaH]

run-ci