Add Eval to Foundry CLI

[KuuCi]

This PR allows users to call composer llm-foundry eval {YAML_PATH} {ARGS} while maintaining correctness with existing evaluation script. The motivation is for DLE where we want to make the CLI much more intuitive in the docker images

[KuuCi]

Working tests:
test-eval-rdrmLF runs:
composer -c llmfoundry eval eval/yamls/hf_eval.yaml || (echo "Command failed - killing python" && pkill python && exit 1)

test-eval-qQI2O7 runs:
composer -n 8 -c llmfoundry eval eval/yamls/hf_eval.yaml || (echo "Command failed - killing python" && pkill python && exit 1)

test-eval-jG8CT2 runs:
composer llmfoundry eval/eval.py eval/yamls/hf_eval.yaml || (echo "Command failed - killing python" && pkill python && exit 1)

[b-chu]

Is there a better name for the llmfoundry/train folder?

[irenedea]

I don't think we should have llmfoundry.train.eval. That naming doesn't make sense to me.

[b-chu]

llmfoundry.train.train also doesn't seem great

[KuuCi]

Test run too show working [Updated]:

mcli logs test-eval-cli-U54lW1:
composer -n 8 -c llmfoundry eval eval/yamls/hf_eval.yaml || (echo "Command failed - killing python" && pkill python && exit 1)

mcli logs test-eval-orig-5TibQk:
composer eval/eval.py eval/yamls/hf_eval.yaml || (echo "Command failed - killing python" && pkill python && exit 1)

stale