Allow empty task id in entity statuses for new geopoint

[Sujanadh]

What type of PR is this? (check all applicable)

• 🍕 Feature
• 🐛 Bug Fix
• 📝 Documentation
• 🧑‍💻 Refactor
• ✅ Test
• 🤖 Build or CI
• ❓ Other (please specify)

Related Issue

Whenever new geopoint is introduced it won't have task_id since we don't have task_id filter any more so there won't be task id for new feature which resulted into validation error in entity statuses endpoint.

• related issue Submission count in infographics page is not updated when custom coordinate upload #1711

Unrelated to entity statuses , I encountered an issue in preview_split_by_square where aoi is changed when single polygon is uploaded.

Actual AOI:

After merge_polygons:

Describe this PR

This PR updates the schema EntityTaskID and EntityOsmID in order to allow empty task_id and osm_id which likely occurs if new feature geopoint is introduced in submissions. This PR also updates the function preview_split_by_square where the length of polygon is checked before in order to apply merge_polygons only for multipolygon aoi.

This PR depends on the new release of osm-fieldwork for the creation of new entity id for new feature geopoint.

Screenshots

N/A

Alternative Approaches Considered

Did you attempt any other approaches that are not documented in code?

Review Guide

Notes for the reviewer. How to test this change?

Checklist before requesting a review

• 📖 Read the FMTM Contributing Guide: https://github.com/hotosm/fmtm/blob/main/CONTRIBUTING.md
• 📖 Read the HOT Code of Conduct: https://docs.hotosm.org/code-of-conduct
• 👷‍♀️ Create small PRs. In most cases, this will be possible.
• ✅ Provide tests for your changes.
• 📝 Use descriptive commit messages.
• 📗 Update any related documentation and include any relevant screenshots.

[optional] What gif best describes this PR or how it makes you feel?

[spwoodcock]

Very nice use of Pydantic 👏