HotFix: Updated the xform in form fields

[Sujanadh]

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

• 🍕 Feature
• 🐛 Bug Fix
• 📝 Documentation Update
• 🎨 Style
• 🧑‍💻 Code Refactor
• 🔥 Performance Improvements
• ✅ Test
• 🤖 Build
• 🔁 CI
• 📦 Chore (Release)
• ⏩ Revert

Related Issue

• Fixes Crashing of submission table page #1297

Describe this PR

This PR addresses the updated xform name in the form fields endpoint, solving the crashing issue.

Screenshots

N/A

Checklist before requesting a review

• 📖 Read the FMTM Contributing Guide: https://github.com/hotosm/fmtm/blob/main/CONTRIBUTING.md
• 📖 Read the FMTM Code of Conduct: https://github.com/hotosm/fmtm/blob/main/CODE_OF_CONDUCT.md
• 👷‍♀️ 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, thank you 👍

I will cherry pick this commit into staging and main for now.

Just a quick update on the meaning of hotfix @nrjadkry @Sujanadh

A hotfix is to address a high priority bug in production that can't wait until the next deployment cycle.

It's a method to bypass the usual processes of waiting to merge dev --> stage --> main.

So a hotfix should probably be based off the main branch and the PR made to the main branch, if it's a genuine hotfix. In this case I think it is as production could really do with this change (without adding all of the other code on dev that may introduce other bugs).

Another approach could be to make the PR to dev, then cherry pick the commit through to production. But if the code is quite out of sync between dev and main, then this can be more difficult.

[Sujanadh]

got it 🙌