Use default odk creds when organisation do not have their own during project creation

[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: Provide organisational admins with ODK credentials if needed #2056

Describe this PR

If the organisation used during project creation do not have their own odk credentials, then we allow them to create project with our own default odk credentials without exposing it.

• checks if org has their own credentials, if not use default creds from env.

Screenshots

N/A

Alternative Approaches Considered

Tried using credentials from hotosm organisation, but thought to use them from env instead to avoid extra db call.

Review Guide

• create new organisation without odk creds and use it during project creation.

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]

Frontend changes

• As default, there will be option to tick the check box to use default odk creds
  
• if the org already has odk creds, the check box is ticked automatically here
  
• Naxa org here do not have creds, still can use default creds by checking the box
  

[spwoodcock]

Looks good 👍

I thought we would go the route of inserting the default creds into the org during org creation, if none provided.

This approach also works. It actually has the advantage that we can update the default creds in the env at any point