refactor!: replace DepthTo3DLocations sensor args with SensorConfig sequence

[TimothyAlexisVass]

Follow-up to

• refactor: Fix simple ANN001 violations - Part 1 #835

@tristanls-tbp

suggestion (non-blocking, different pull request): There's an opportunity here to only accept Sequences. It is trivial to specify a sequence of one, so I'd rather we do that in the code then having to deal with if isinstance(thing, (int, float)):.

suggestion (non-blocking, different pull request): Seeing how we multiply zooms and hfovs to match length of sensor_ids, points to that we could better configure things by accepting a Sequence[SensorConfig] or something similar that has all the data we need.

Summary

This follow-up PR removes legacy parallel/union constructor inputs from DepthTo3DLocations and enforces a single, typed configuration path via Sequence[SensorConfig].

Changes

• DepthTo3DLocations.__init__ now requires sensor_configs: Sequence[SensorConfig].
  • The legacy arguments sensor_ids, resolutions, zooms, and hfov were removed.
  • The constructor now accepts only typed sensor configuration objects and drops scalar acceptance for zoom/FOV.
• Main changes are in src/tbp/monty/frameworks/environment_utils/transforms.py

Most of the files changed are .yaml configs and snapshots, updated to the new SensorConfig contract:

% git diff main --name-only -- . ':(exclude)*.yaml'
src/tbp/monty/frameworks/environment_utils/transforms.py
src/tbp/monty/frameworks/environments/two_d_data.py
tests/unit/frameworks/environment_utils/habitat_transform_test.py

Scope / Behavior

• In-repo callers already using SensorConfig continue to work.
• This PR is a stricter, typed follow-up and intentionally removes old construction paths for DepthTo3DLocations.

⚠️ Follow-up / Risk

• Breaking change for any external code that still calls DepthTo3DLocations with old positional args (sensor_ids, resolutions, zooms, hfov) and is not migrated to SensorConfig.
  If any unexpected callers require backwards-compatibility to the legacy arguments, that is already prepared and we could drop commit 305b918.

[tristanls-tbp]

note: Added breaking change ! indicator to the PR title since this is a breaking change and requires users to change how they configure Monty.

[TimothyAlexisVass]

@tristanls-tbp If we want backwards compatibility instead of making this a breaking change, I did prepare that.
I wasn't sure what the convention is in this project. So, if we want it, we can drop the commit that removed that preparation:
Remove backwards compatibility for external callers

[tristanls-tbp]

note: Apologies, but I intend to delay review of this and other config-altering PRs until after #857 is merged. I know that #857 wasn't around when you submitted the PR, but it's big and took a lot of validation work.

[tristanls-tbp]

Hi @TimothyAlexisVass, ok, we reworked how we do configurations in #857, which is now merged.