Improve PEFT UX
jenkins
# What does this PR do ?

Two improvements of PEFT UX
1. Correct layer_selection logging messages in the case of more than one adapters.
2. Make output (label, ground truth) field optional for test data, for use cases where user only wants to generate text with gpt_peft_eval and not calculate any metrics. 
   - Note that using the default config file, `data.test_ds.label_key` and `data.test_ds.prompt_template` still reference an "output" field. These do not need to be changed. This PR simply ignores a key error if `data.test_ds.label_key` does not exist in the test data file.


**Collection**: NLP

# Jenkins CI
To run Jenkins, a NeMo User with write access must comment `jenkins` on the PR.

# Before your PR is "Ready for review"
**Pre checks**:
- [ ] Make sure you read and followed [Contributor guidelines](https://github.com/NVIDIA/NeMo/blob/main/CONTRIBUTING.md)
- [ ] 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
- [x] User Experience Improvement

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](https://github.com/NVIDIA/NeMo/blob/main/CONTRIBUTING.md) contains specific people who can review PRs to various areas.

# Additional Information
* Related to # (issue)
