[BUG] Fix Incident Mapping Errors

[DMalone87]

Describe the bug
Both the search page and the incident view page are failing to properly map incidents. On the Search page with the map, the incidents are not showing up as markers on the map.

On the Results page, there's a crash as soon as you attempt to load.

To Reproduce
Steps to reproduce the behavior:

1. Register/Log in
2. Navigate to /search (You may need to refresh the database as we've made a number of changes)
3. Attempt a search with no search terms entered. You should see all results returned. There will be no markers on the map.
4. Click the "Full >" Link on one of the records.

Expected behavior
When a search is entered, all of the results from that search should show up as markers on the map. When you click on the Full link, you should be taken to a page where the location of the incident is shown on a satellite map.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: Desktop
• OS: Ventura
• Browser Safari
• Version 16

[DMalone87]

One issue I noticed right off the bat: on this page, incident.locationLatLon doesn't actually return anything as the code is written now. If we want to return a value this way, we'll need to add a function to the Incident Model.

I tried making the existing location.longitude and location.latitude (which are being filled) into an array, but that didn't seem to work even though it fits the expected data.

  const createFeature = (incident: Incident) => {
    const feature: Feature = {
      type: "Feature",
      properties: { ...incident, locationLonLat: projection([incident.longitude, incident.latitude]) },
      geometry: { type: "Point", coordinates: projection([incident.longitude, incident.latitude]) }
    }
    return feature

[DMalone87]

@sashamaryl, I know it's been a while, but do you have any thoughts?

[DMalone87]

Some additional insight into the issues here:

1. There's a reference to an API key meant to be delivered through an environment variable, NEXT_PUBLIC_MAPS_KEY, that doesn't actually exist outside of the two files that attempt to call it, Incident View Header Index and Incident Google Map Index.
2. The Google Maps API Loader is invoked twice on the Incident View page, once in the header and once for the map itself. This double loading itself causes an error once the key is added. Also, the header invokation appears to fail anyway, even if with a valid key.

[DMalone87]

These functions (Search Panel Map) are coming from D3: https://github.com/d3/d3-geo