Issue Number: (214)

Close microsoft#214

Summary

Handle scenarios where location files with the same NamedGeoposition key can be overwritten by another file.

Changes

• Rename dup keys to allow to be all loaded, avoiding name collision and user missing Geoposition instances.
• For instance:
  • If a there is a Geoposition eastus on file1.json and in file2.json, loading both files, it would ensure that both Geopositions are loaded. eastus on file2.json can be indexed as eastus_1. User could now retrieve that instance using eastus_1 instead of not be able to find it (current behavior). If there is another one, on a 3rd file, it would be eastus_2 and so on.

Checklist

• Local Tests Passing?
• CICD and Pipeline Tests Passing?
• Added any new Tests?