fix: store nodes preferences in nodes.json using homeHex

[robertsLando]

Fixes #3817

[coveralls]

Pull Request Test Coverage Report for Build 12990086483

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 63 (0.0%) changed or added relevant lines in 2 files are covered.
• 1 unchanged line in 1 file lost coverage.
• Overall coverage decreased (-0.04%) to 21.018%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
api/config/store.ts	0	1	0.0%
api/lib/ZwaveClient.ts	0	62	0.0%

Files with Coverage Reduction	New Missed Lines	%
api/lib/logger.ts	1	89.27%

Totals
Change from base Build 12866617879:	-0.04%
Covered Lines:	3952
Relevant Lines:	20000

---

💛 - Coveralls

[AlCalzone]

Does this gracefully handle existing nodes.json? It's not entirely clear to me how much magic is behind the scenes.

I wouldn't want to delete all names and locations for users who have them set.

[AlCalzone]

Ok, let me do a quick test

[AlCalzone]

We should probably also clean up these entries when migrating:

[robertsLando]

@AlCalzone done

[AlCalzone]

Also, should we delete entries when hard-resetting the controller? Afterwards the current home ID is "lost", unless someone restores an NVM backup. Not entirely sure.