Implement LOI property generator for GeoIDs

[rfontanarosa]

closes #2438
closes #1537
closes #2113

[gino-m]

Please also update the PR description to something a bit more self-descriptive, e.g., "Implement property generator for GeoIDs"

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 62.58%. Comparing base (ce86519) to head (8693ab8).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #2484   +/-   ##
=======================================
  Coverage   62.58%   62.58%           
=======================================
  Files         120      120           
  Lines        2865     2865           
  Branches      425      425           
=======================================
  Hits         1793     1793           
  Misses       1012     1012           
  Partials       60       60           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[gino-m]

Doesn't WHISP already issue geoIDs? Why do we need a separate generator for GeoIDs?

[jo-spek]

Doesn't WHISP already issue geoIDs? Why do we need a separate generator for GeoIDs?

GeoIDs are supposed to be the ultimate pilar of interoperability. So that a geometry created in Ground can easily be loaded elsewhere without having to export import. If you would generate GeoIDs in Whisp, you would have to manually export-import from Ground to Whisp. We want any newly created geometry to have a GeoID immediately.