Fixed reading geometryXPath in FormMetadataParser

[grzesiek2010]

Closes #6450

Why is this the best possible solution? Were any other approaches considered?

The problem here was a bug in a recursive function that returned a wrong (null) value too early.

How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?

We should test forms with geopoints (those that display the map icon in the form list) under different configurations. In this case, the issue was that while the geopoint existed, the form had two groups, and it was placed in the second one. It would be helpful to create several forms with multiple groups, including nested ones, to thoroughly test these scenarios.

Do we need any specific form for testing your changes? If so, please attach one.

No.

Does this change require updates to documentation? If so, please file an issue here and include the link below.

No.

Before submitting this PR, please make sure you have:

• added or modified tests for any new or changed behavior
• run ./gradlew connectedAndroidTest (or ./gradlew testLab) and confirmed all checks still pass
• added a comment above any new strings describing it for translators
• added any new strings with date formatting to DateFormatsTest
• verified that any code or assets from external sources are properly credited in comments and/or in the about file.
• verified that any new UI elements use theme colors. UI Components Style guidelines

[dbemke]

Tested with Success!

Verified on a device with Android 10

Verified cases:

• issue Missing form map in All widgets/ All question type in "Start new form". #6450 doesn't occur
• forms with geopoint in groups and nested groups
• quick regression checks in maps

[WKobus]

Tested with Success!

Verified on a device with Android 15