[mujoco] Add native MyoSuite env families and validation

[Trinkle23897]

Description

This PR finishes the native EnvPool MyoSuite integration on top of the earlier intake work.

Implemented surface:

• MyoBase native families, including the full Reorient / Walk / Terrain task sets
• MyoChallenge native families, including Reorient, Relocate, Baoding, Bimanual, RunTrack, Soccer, ChaseTag, and TableTennis
• MyoDM native TrackEnv, covering the full generated TrackEnv surface

What landed:

• native C++ runtime implementations for the remaining MyoSuite families under envpool/mujoco/myosuite/
• pybind and Python wrapper wiring for all new native specs / pools
• metadata-driven coverage for the full upstream MyoSuite surface we stage locally
• deterministic tests, representative oracle alignment tests, and pixel smoke coverage for the new MyoSuite families
• Windows GLFW preload for MyoSuite pixel tests so the Mujoco renderer comes up consistently in CI

Motivation and Context

The initial intake PR only pinned upstream assets and generated metadata. This follow-up closes the loop by registering and validating the actual native EnvPool runtime for the staged MyoSuite families.

The main implementation goal here is not a representative subset but the intended upstream task surfaces for:

• myobase
• myochallenge
• myodm

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds core functionality)
• New environment (non-breaking change which adds 3rd-party environment)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation (update in the documentation)
• Example (update in the folder of example)

Implemented Tasks

• Register the native MyoBase families and cover the full Reorient / Walk / Terrain surfaces
• Register the native MyoChallenge families and cover the full intended challenge surface
• Register the native MyoDM TrackEnv surface from generated metadata
• Add deterministic / alignment / pixel smoke coverage for the new MyoSuite families
• Fix CI-specific MyoSuite renderer setup on Windows tests

Validation

Run locally:

• git diff --check
• ruff check envpool/mujoco/myosuite/native.py envpool/mujoco/myosuite/myobase_test.py envpool/mujoco/myosuite/myochallenge_test.py envpool/mujoco/myosuite/myodm_test.py
• bazel test --test_output=errors //envpool/mujoco:myosuite_myobase_test //envpool/mujoco:myosuite_myochallenge_test //envpool/mujoco:myosuite_myodm_test

Checklist

• I have read the CONTRIBUTION guide (required)
• My change requires a change to the documentation.
• I have updated the tests accordingly (required for a bug fix or a new feature).
• I have updated the documentation accordingly.
• I have reformatted the code using make format (required)
• I have checked the code using make lint (required)
• I have ensured make bazel-test pass. (required)