fix: determine correct projection from features at getProj

[silvester-pari]

Implemented changes

This fixes the "guessing" of feature projection based on content. It was working for Polygons, but for other types (Point, MultiPolygon etc.) the accessing of the reference coordinate was either one level "too high" or "too low". This PR introduces a new helper function findFirstCoordinateValue that recursively gets the first number and uses that as reference coordinate.

This is used at the eox-map parseFeatures method, which is also used inside of eox-drawtools.

Screenshots/Videos

Before

After

Checklist before requesting a review

• I have performed a self-review of my code
• All checks have passed
• I have added a test for this fix
• The PR title follows conventional commit style and reflects the type of change (major/minor/patch, breaking)
• The PR title describes the change within this element (each merged PR equals one entry in the element's changelog!)

[netlify]

✅ Deploy Preview for eoxelements ready!

Name	Link
🔨 Latest commit	ecd405b
🔍 Latest deploy log	https://app.netlify.com/projects/eoxelements/deploys/691f089e48ad3100075023c3
😎 Deploy Preview	https://deploy-preview-1959--eoxelements.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[RobertOrthofer]

this is correct, the epsg codes were switched 👍