Stop blocking the addition of new points when constraint fails

[grzesiek2010]

Closes #7191

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

The decision to unblock adding new points is a result of our internal discussions. There is nothing worth discussing regarding implementation changes.

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 not block adding new points when a geoshape/trace is invalid. We should still display errors and highlight the geotrace/geoshape in red, and block saving, but allow the user to fix the issue by adding new points.
There is no need to test every map engine, we can focus on one.

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

I used: geo.xlsx

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

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

[WKobus]

Tested with success

Verified on Android 16

Verified cases:

• Adding, moving and removing points in forms with intersects and incremental
• Regression checks on geo widgets
• Horizontal and portrait view
• Different map sources

[dbemke]

Tested with success

Verified on Android 10