Fixes #197 : Improve Pin Clustering and Selection on ExploreScreen

The goal of this PR is to enhance the functionality of the map on the ExploreScreen by introducing clustering behavior for pins and improving the usability of selecting individual pins. When multiple pins overlap due to being in close proximity, they now form a cluster, which the user can click to zoom into. Once zoomed in, individual pins can be selected, and their associated notes are displayed correctly in the horizontal scrollbar.

Why Was It Changed?

Previously, users experienced confusion when trying to interact with pins that overlapped on the map. Clicking on one pin could result in navigating to a different pin or just taking it to the ocean, displaying incorrect notes in the scrollbar. This made it difficult to explore notes effectively in the map.

By implementing clustering and improving pin selection behavior, the map becomes more intuitive and user-friendly, ensuring users can focus on their ethnographic work without navigation issues.

How Was It Changed?

Clustering Behavior:

• Pins that are close together in a zoomed-out view now form clusters.
• Clicking on a cluster zooms into the area to reveal individual pins.

Pin Selection:

• Users can select individual pins once the cluster is expanded.
• Clicking on a pin fetches and displays the correct note in the horizontal scrollbar.

Code Updates:

• Added a haversineDistance function to calculate proximity between pins.
• Updated onMarkerPress to handle clustering and selection logic.
• Modified MapView settings to animate zooming into clusters and ensure individual pin selection works seamlessly.

Styling Enhancements:

• Introduced a clusterMarker style for clustered pins.
• Adjusted the pin animation for improved visibility during selection.

Test Cases:

• Validated that clusters zoom in correctly when clicked.
• Ensured that individual pins fetch and display the correct notes.

While the idea and functionality seems to be able to work and theoretically works, I was able to update some of the functionality, but I added a little more and started coming across the same issues, attached below. I am creating this PR after trying 3 different methods to solve this problem and spending many hours, but I hope to show any additions and changes that I make to this code as soon as possible and can completely solve it.