fix/6373 project name input validation

[royallsilwallz]

• Prettier
• Update node versions used in CI and docker images
• Initial frontend dependency updates
• Drop polyfills
• ReactJS: update root rendering method
• Load only necessary translations
• Wrap methods which affect UI by act in tests
• React Tooltip v4 -> v5 adaptions
• Update test message
• Fix query-string usages
• Fix infinite recursion due to state changes
• Use CRACO to workaround CRA #11770
• Fix tests
• ReactJS: Fix "
  cannot appear as a descendant of

  " warnings

• Fix forwardRef warnings
• commentInput: Ensure react-md-editor is not part of the main chunk
• Improve treeshaking
• fixup! Improve treeshaking
• Revise implementation to insert testimonial image
• Fix tests again
• internationalization: Fix Sonar issues for promises with no exception handling
• Add JOSM responses to server-handlers
• Fix navigation on point click
• Testing-Library: Increase default timeout
• project.test.js: Attempt to fix resource leak by waiting for rendering to finish
• Fix Rapid imports for newer build-time dependencies
• Cancel call to ohsome when a component is unloaded
• Explicitly import lazy imports in tests
• Fix failing test in projectStats.test.js by waiting for text
• Add default changeset comment from env in ohsome API
• docs: fix readme landing page screenshot
• Simplify docker image tags
• Shorten workflow name
• Fix container image name
• Fix container image name
• Revert "Fix container image name"
• Revert "Fix container image name"
• Validate empty project name while creating project
• Validate symbols and number in first charater of project name

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

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

Related Issue

Example: Fixes hotosm#123

Describe this PR

A brief description of how this solves the issue.

Screenshots

Please provide screenshots of the change.

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 Tasking Manager Contributing Guide: https://github.com/hotosm/tasking-manager/blob/develop/docs/developers/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?