chore: Update Marker type from Google Maps API

[russchristina]

This small PR slightly refactors a bit of the UI-related code to use the new Marker type from the Google Maps API. The new Marker type has a slightly different implementation from its predecessor; it uses properties where its predecessor used methods instead, so my changes reflect this difference.

Pull Request type

Please check the type of change your PR introduces:

• Bugfix
• Feature
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no API changes)
• Build-related changes
• Documentation content changes
• Other (please describe): General maintenance

What is the current behavior?

No behavior should be modified. The use of new Marker type shouldn't change the behavior. It just uses Google Maps API's new implementation for the Marker.

Issue Number: 947

What is the new behavior?

There is no new behavior as stated above.

Does this introduce a breaking change?

• Yes
• No

Other information

[alwaysmeticulous]

🤖 No test run has been triggered as your Meticulous project has been deactivated (since you haven't viewed any test results in a while). Click here to reactivate.

_{Last updated for commit 27ae56b. This comment will update as new commits are pushed.}

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
inreach-app	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Mar 18, 2024 2:51pm

[github-actions]

📦 Next.js Bundle Analysis for @weareinreach/app

This analysis was generated by the Next.js Bundle Analysis action. 🤖

This PR introduced no changes to the JavaScript bundle! 🙌

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud