create a table to store bad and new geoms

[Sujanadh]

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

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

Related Issue

• Issue: Create new DB table to store 'new' and 'bad' geoms #1986

Describe this PR

This PR creates a table to store geometry with status 'BAD' or 'NEW'.

Response

{
  "geom": {
    "type": "Polygon",
    "coordinates": [
      [
        [
          85.333952,
          27.699157
        ],
        [
          85.333892,
          27.699038
        ],
        [
          85.33404,
          27.699001
        ],
        [
          85.334109,
          27.699095
        ],
        [
          85.333952,
          27.699157
        ]
      ]
    ]
  },
  "status": "NEW",
  "project_id": 3,
  "task_id": 1
}

Endpoint:

/projects/{project_id}/geometries

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]

Nice work 👍

Don't forget the db init script though =)
(So the table exists on a new FMTM instance without migrations)

[Sujanadh]

Oh yeah. okay 👍