Investigate Mapbox API usage to inform billing

[jilladams]

Description

Via #19201 we learned that our Mapbox Temporary Geocoding API usage aligns with Facility Locator search calls.

Our monthly invoicing includes calls to many other APIs, and we'd like to try to align those to usage to determine whether:

1. Calls being made are useful / necessary
2. Calls are being made from Sitewide products

Usage

API	September 2024 usage	October 2024 usage
Permanent Geocoding API	4 requests	9 requests
Map Loads for Web	837,440 loads	871,572 loads
Static Images API	1,053,302 requests	1,168,345 requests
Matrix API		130,356 matrix elements

task list, maybe

• Check content-build and vets-website code for Mapbox calls
• Gather a list of which kinds of pages make which kinds of calls
• Ask Product to help compare those pages to analytics / traffic, in order to know if our usage amounts to the API call volume

ACs

• Document which pages make which API calls in the Mapbox docs (which are in FL, and may need to move later)
• [ ]

[jilladams]

From product sync:

• We don't think this ticket blocks autocomplete next steps.
• We need engineering to help assess where we make calls.
• Product will then need to map those uses to analytics to know the multiplier for which calls end up being expensive in terms of page views or number of times we're making the calls.
• Then: we can figure out where we can be more efficient -- alternate ways to achieve the same functionality with fewer Mapbox calls, etc.