refactor: update sizes of clusters

[emilyjablonski]

This PR addresses #1074

• Addresses the issue in full
• Addresses only certain aspects of the issue

Description

Following the map release, given the specific data set we have in production, we're less satisfied with the cluster sizes compared to what was in staging. The cluster sizes feel as though they are not big enough compared to a single pin, and there's not enough disparity between clusters of different numbers. Google has a few different algorithms you can use for clustering.

I updated some settings on one of their algorithms and increased slightly both the size and disparity between clusters.

How Can This Be Tested/Reviewed?

This has been approved w design.

This PR with updated cluster algorithm and slightly larger size and disparity:

Production:

Author Checklist:

• Added QA notes to the issue with applicable URLs
• Reviewed in a desktop view
• Reviewed in a mobile view
• Reviewed considering accessibility
• Added tests covering the changes
• Made corresponding changes to the documentation
• Ran yarn generate:client and/or created a migration when required

Review Process:

• Read and understand the issue
• Ensure the author has added QA notes
• Review the code itself from a style point of view
• Pull the changes down locally and test that the acceptance criteria is met
• Either (1) explicitly ask a clarifying question, (2) request changes, or (3) approve the PR, even if there are very small remaining changes, if you don't need to re-review after the updates

[ColinBuyck]

LGTM 🧼