feat: new empty state for additional map markers

[emilyjablonski]

This PR addresses #1049

• Addresses the issue in full

Description

The issue has more details, but the PR creates two distinct empty states for the map - 1) there are no matching listings anywhere and the map is empty 2) there are no matching listings in the spot you're viewing in the map, but there are listings elsewhere, you just need to recenter

How Can This Be Tested/Reviewed?

Test each empty state - for the new state, see the new copy and the new button that will automatically re-fit the bounds of the map on the current markers (the only other time we fit bounds is on initial page load)

1. No matching listings - Set a filter where no listings will match, and see the empty state indicate there are no matching listings and that you need to adjust your filters
2. No visible listings - A. Scroll all the markers off the screen and see the new empty state indicating there are no markers in the search area, and click the button to reset your bounds. B. Zoom in on a single pin. Set a filter that will remove that pin from the view, but will keep other pins visible, like filtering on a different county. Click the button to reset your bounds.

Author Checklist:

• Added QA notes to the issue with applicable URLs
• Reviewed in a desktop view
• Reviewed in a mobile view
• Reviewed considering accessibility / It resets the view, but could likely be improved with a specific screen reader announcement - it keeps the focus in the list which I think is preferable
• Added tests covering the changes / Not having integration tests on this page would make this a hefty setup. We're refining tickets for more public side integration tests too! Frontend integration tests for the Doorway map/directory page #1050
• 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

[jaredcwhite]