Eliminate waymo_open_dataset dependency

[saulfield]

Fixes #1880

[Gamenot]

I am cautious about naming the package the same as the original. It might cause a package conflict.

[saulfield]

I am cautious about naming the package the same as the original. It might cause a package conflict.

I agree in general, but in this case I think it's ok. It makes it easier since we don't have to modify any of the protos or generated files to make the imports work, and since the waymo package is incompatible with smarts anyway there isn't a risk of them being installed in the same venv.

[Gamenot]

OK.

[Adaickalavan]

Some thoughts on presenting SMARTS support for external datasets. We could address this in a separate PR too.

Consider updating how to use SMARTS for Waymo in ReadTheDocs::Ecosystem::Waymo.

In ReadTheDocs::Example::Naturalistic section we could provide intructions
(e.g., scl run --envision examples/<script_name>.py scenarios/<scenario_name>)
to run a simple ego agent (e.g., AgentType.Laner, etc) on a Waymo map with traffic (e.g., dataset="training_20s.tfrecord-00022-of-01000" and scenario_id="62662fab4d63c247"). We could then post a gif of the replayed Waymo scenario showing the expected outcome. To reproduce the result, we could instruct the users to download and edit the dataset path in the provided script prior to executing the instructions.

We could move readmes such as (i)SMARTS/scenarios/waymo/README.md, and (ii) SMARTS/waymo_open_dataset/README.md, to ReadTheDocs::Ecosystem::Waymo .

[saulfield]

I moved the waymo_open_dataset module to smarts/waymo because there were some issues with finding the module path from within smarts.

I also updated the Waymo section of the docs, and deleted the README in the waymo example scenario.