pypi compatibility

[cmunley1]

• search cwd for env.yaml and for config paths provided to ng_run.
• use importlib.metadata for ng_help
• modify server requirements.txt or pyproject.toml to use pypi nemo-gym rather than ../../ relative path

basic tests done of ng_run and ng_collect_rollouts with an environment outside of Gym/.

I think that we should really consider a few things, but maybe we stick to minimal changes for now:

• packaging environments separately
• moving resources_servers etc inside nemo_gym to have only 1 entrypoint in sitepackages, i find it strange to have site-packages/resources_servers
• giving user clear guidance on proper way to make new env with pip installed gym. Mocking Gym repo structure is 1 option

[copy-pr-bot]

Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually.

Contributors can view more details about this message here.

[cmunley1]

this should be removed after testing on this branch is done

[cmunley1]

this should be removed when we are ready to push to pypi (not test pypi)

[cmunley1]

i dont really like this, sed to remove this block of vllm_model pyproject.toml, but it was error otherwise. could cause trouble if we needed tool uv sources for something else in vllm-model, but i doubt that happens.

I feel in general this runtime server deps patching is not ideal and we should have a different longer-term solution (like reorganize all under nemo_gym might solve this)

[cmunley1]

to test:
uv pip install --index-url https://test.pypi.org/simple/ --extra-index-url https://pypi.org/simple/ nemo-gym==0.2.9172rc0 , create local resources server (just copy paste one out of Gym and change name), and run rollouts.