Fix Multi-NF failure

[jordlay]

---

Problem:
When multiple nf RETs were defined in nsd-input.jsonc, there would be 2 RETs in the NSDV but they would be identical, there would also only be one mapping file. This was due to the previous design decision to call the RETs the NSD name and version, instead of the NF name.

Fix:

• Changed processor and artifacts to use nf name instead of nsd name

Testing:

• Testing single nf still behaves as expected with cnf to sns - ongoing

• Test NSDV republish with same values

• Test NSDV republish with different values

• Test multi nf to sns with 2 CNFS:
  

This checklist is used to make sure that common guidelines for a pull request are followed.

Related command

General Guidelines

• Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
• Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)

For new extensions:

• My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish

There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

[patrykkulik-microsoft]

Looks good to me