Support v2 nested property names

[doneill]

EarthRanger v2 JSONForms schema spec is introducing support whereby the schemas UI should support nested properties with a shared name. E.g. report.name and report.area.name shouldn’t have a name conflict just because both contain a property called name

Action

• Add support in src/v2/utils.ts to support ui.fields using globally unique IDs, not names, for collection item fields
• Add test to specifically validate the collision scenario

Expectation:

• Client apps should continue to display forms correctly where the same property name exists at multiple levels and confirm each level gets its own property