[NLP] Use register_artifact from superclass directly
I don't know why we need this. It breaks a bunch of things at this point. Is it worth it to change it? > I don't know why we need this. It breaks a bunch of things at this point. Is it worth it to change it?

That's quite surprising.. Let me retry the Jenkins pipeline.

I'm not insisting on that though, it's a small cleanup which should be harmless. jenkins Eric pointed out that default for `verify_src_exists` is different across the two classes, which I missed. Hence pipeline fails.

I'll figure that out as I think it's worth it as a simplification This PR is stale because it has been open for 14 days with no activity. Remove stale label or comment or update or this will be closed in 7 days. This PR is stale because it has been open for 14 days with no activity. Remove stale label or comment or update or this will be closed in 7 days. This PR was closed because it has been inactive for 7 days since being marked as stale.
# What does this PR do ?

Removes explicit code to call superclass method (cleanup).

**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**:
- [x] 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**:
- [x] Improvement

## 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 https://github.com/NVIDIA/NeMo/pull/7935
