feat: protected feature API

[eatyourgreens]

• a new API, /features/{protector-feature-id}/protected-by, which returns list of adaptation options, by feature and layer, for all features protected by protector-feature-id.
• a new recoil selector, which runs the query when the current selected feature ID changes.
• new recoil selectors that filter the results by RCP and protection level.
• overlaps with refactor(backend): replace db.query() with select() #213 as the new endpoint uses select() to generate queries.
• data loader layers now take an optional dataFetcher option, a function returning a Promise that resolves to a list of feature IDs and values.
• a new feature in the frontend, where preloaded adaptation data can be injected into individual data layers. The exact layer API will probably change, but it currently uses a Map, which stores feature adaptation data mapped by layer ID:

  viewLayers.map((viewLayer) => {
    const viewLayerParams = viewLayersParams.get(viewLayer.id);
    const data = viewLayersData?.get(viewLayer.id);
    const deckProps = {
      id: viewLayer.id,
      pickable: !!viewLayer.interactionGroup,
      beforeId,
    };
    return viewLayer.fn({
      deckProps,
      zoom,
      ...viewLayerParams,
      data,
    });
  });

Here, selecting the airport runway runs a query that returns a list of water infrastructure features, styled by the selected adaptation variable.

720p.Screen.Recording.2024-12-10.at.08.41.28.mov

[eatyourgreens]

a new recoil selector, which runs the query when the current selected feature ID changes.

I think there's a possible scenario/user story where I'd select a protector feature, to show all linked, protected features, then click on a protected feature to select that and see more detail. At the moment, that would clear the protected feature query, when the selected feature ID changes. The query results might need to persist, as long as we're interacting with protected features.