Feat project details geolocation integration

[NSUWAL123]

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

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

Related Issue

Also solves #1343

Describe this PR

This PR covers the following things:

1. Remove geolocation from projectListMap component(HomePage)
2. Generate Mbtiles btn shift to bottom for mobile view
3. Only ask permissions if the geolocation status is turned on

A brief description of how this solves the issue.

Screenshots

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 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?

[NSUWAL123]

@spwoodcock , @varun2948 . It seems that some of the browser doesn't support AbsoluteOrientationSensor.
That's why Sam's laptop was showing page crash error. I think we need another workaround to get phone's quaternion.

Error on firefox:

Absolutely working fine on chrome:

[varun2948]

We mostly used this in mobile and most of the android is based on chromium and chrome so i think it will not be that much of a problem. What's your say @spwoodcock ?

[spwoodcock]

Damn, didn't realise that!

I thought the error on Firefox was because of my privacy settings / disabled geolocation.

At the very least we shouldn't have an error if not available. It should be caught gracefully and displayed to the user that no geolocation is available.

This will be perfect for the demo, but we probably also need to support Safari in the future too (I'll merge this and make an issue for another PR)

[NSUWAL123]

@spwoodcock, fixed the page crash error on another PR