Remove code related to nemo-evaluator (aka nemo-eval)

[athitten]

Important

The Update branch button must only be pressed in very rare occassions.
An outdated branch is never blocking the merge of a PR.
Please reach out to the automation team before pressing that button.

What does this PR do ?

• As evaluation specific code is being placed its own repository under NVIDIA-NeMo org: https://github.com/NVIDIA-NeMo/Evaluator this PR removes all nemo-evaluation and corresponding deployment code specifically from: nemo/collections/llm/evaluation/ and nemo/collections/llm/deploy/
• Also removes corresponding docs from: docs/source/evaluation/
• Removes requirements/requirements_eval.txt and eval setup from setup.py
• Removes nemo-run script for evaluation: scripts/llm/evaluation.py
• Removes tests under tests/evaluation/ and *Eval*.sh files from tests/functional_tests/

Collection: [Note which collection this PR will affect]

Changelog

• Add specific line by line info of high level changes in this PR.

Usage

• You can potentially add a usage example below

# Add a code snippet demonstrating how to use this 

GitHub Actions CI

The Jenkins CI system has been replaced by GitHub Actions self-hosted runners.

The GitHub Actions CI will run automatically when the "Run CICD" label is added to the PR.
To re-run CI remove and add the label again.
To run CI on an untrusted fork, a NeMo user with write access must first click "Approve and run".

Before your PR is "Ready for review"

Pre checks:

• Make sure you read and followed Contributor guidelines
• Did you write any new necessary tests?
• Did you add or update any necessary documentation?
• Does the PR affect components that are optional to install? (Ex: Numba, Pynini, Apex etc)
  • Reviewer: Does the PR have correct import guards for all optional libraries?

PR Type:

• New Feature
• Bugfix
• Documentation

If you haven't finished some of the above items you can still open "Draft" PR.

Who can review?

Anyone in the community is free to review the PR once the checks have passed.
Contributor guidelines contains specific people who can review PRs to various areas.

Additional Information

• Related to # (issue)

[marta-sd]

Thank you @athitten !

I think we also need to remove evaluation code from collections/llm/api, we still have imports and entrypoints for deploy and eval there.

[athitten]

Thank you @athitten !

I think we also need to remove evaluation code from collections/llm/api, we still have imports and entrypoints for deploy and eval there.

Good catch, thanks! Let me remove them

[pablo-garay]

Thank you @athitten !
I think we also need to remove evaluation code from collections/llm/api, we still have imports and entrypoints for deploy and eval there.

Good catch, thanks! Let me remove them

Pylint failing now

[marta-sd]

LGTM, thank you!

[github-actions]

[🤖]: Hi @athitten 👋,

We wanted to let you know that a CICD pipeline for this PR just finished successfully.

So it might be time to merge this PR or get some approvals.

//cc @chtruong814 @ko3n1g @pablo-garay @thomasdhc