Update form by injecting mandatory fields and validate it

[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 Injecting mandatory FMTM fields into custom XLSForms #1722

Describe this PR

This PR depends on osm-fieldwork in order to inject mandatory_fields and digitisation_fields into a custom form if uploaded.

Changes:-

• custom form if uploaded gets updated with mandatory and digitisation fields during form validation
• validate-form used to return a message if the form is valid or not; now it returns form data in bytes along with the message if the form is valid.

Frontend Changes:

• On the frontend side, the bytes returned need to be stored, converted to file and passed during generate-files of project creation
• Or backend changes needed to accept bytes/file both.

Screenshots

N/A

Alternative Approaches Considered

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

Review Guide

N/A

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?

[Sujanadh]

Updates:

decided to return file instead of bytes directly in the response , bytes in the response seems too large and not compatible.

[NSUWAL123]

Updated on frontend as well

• Also addresses issue Disclaimer to inform users that mandatory fields will be injected #1773

[spwoodcock]

Nice coordinated work guys 👍

I just updated osm-fieldwork to 0.16.0 so this should work.
We can update to 0.16.1 with the new feature updates.