Update migration idempotence, add org email field, extra project fields

[spwoodcock]

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

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

Related Issue

#2066
#1979
#1985

Describe this PR

• Tweaks the idempotence of some previous migrations.
• Added extra fields:
  • organisation.associated_email
  • project.geo_restrict_distance_meters (default 50) and geo_restrict_force_error (default false)
  • project.new_geom_type with enum options 'POINT', 'POLYGON', 'LINESTRING'
• Also added these fields to the backend API models: the are returned in responses + allowed during creation POST.

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]

@Sujanadh please merge if you are happy with it 🙏

[Sujanadh]

looks good 👍