Use nodeID for writing record files.

### Background

For realease 0.70 we have to write record files using the nodeId for the record path instead of nodeAccountID.
Also any time we update the nodeAccountID we have to update the table with nodeid/acccountId that the uploader is using

### Acceptance Criteria

- Record files use nodeId in the record path instead of nodeAccountId.
- Mapping table tracks nodeId to nodeAccountId for uploader usage.
- Updating nodeAccountId automatically updates the mapping table.
- Tested the new behavior with HAPI tests

### Dependencies

_No response_

### Definition of Ready (DoR) Checklist

- [ ] Clear acceptance criteria
- [ ] Clear and detailed description
- [ ] Dependencies identified
- [ ] Links to documentation
- [ ] Should be completable in 2-3 Days
- [ ] Initial draft of Low-level design document
- [ ] At least high level test plan
- [ ] Groomed/Estimated

### Definition of Done (DoD) Checklist

- [ ] Acceptance Criteria complete
- [ ] No Codacy issues greater than minor (in new code)
- [ ] JavaDocs updated/created
- [ ] Code commented
- [ ] Unit tests created/updated
- [ ] 80% test code coverage (in new code)
- [ ] Happy Path and major negative cases in HAPI tests as applicable

Locate the code that writes record files, updates nodeAccountID, and maintains the uploader's mapping table; no file paths are specified in the issue. Run the relevant HAPI tests first, then verify record paths use nodeId, mapping entries track both identifiers, and nodeAccountID updates refresh the mapping.

Written by the indexing model from the issue text.