[WIP] Insights product/insights data provider

[vxsl]

Introduced InsightsDataProvider and new special logic for insights data inside Widget.

---

⚠️

until there are Cox users with policies and the ACL is implemented, the InsightsDataProvider won't work unless you use EQWorks/firstorder#687

---

explanation

• multiple widgets with INSIGHTS_DATA data sources should be wrapped in a single instance of InsightsDataProvider that receives a year prop and a month prop (the latter is technically optional in some cases, as some insights data is only refreshed yearly)
• these widgets will send a signal to InsightsDataProvider with the insights data name that they require (for example dta_dealertrack_deals, or visitor_visitation, or dta_census, etc.
• the InsightsDataProvider combines this information from its children with the current month and/or year to fetch all the requested data and pass it back to each widget. Side benefit is that API requests are deduplicated if there is more than one widget that requests the same data.

Note that firstorder automatically scopes the data to the dealer ID embedded in the user's access object.

---

explanation of the InsightsDataProvider story

I've created+used widgets with the following IDs to demonstrate the new functionality: 100056, 100057, 100058, and 100084. These are copies of 56, 57, 58 and 84 respectively with the only difference being that the data source has changed from something like this:

  "dataSource": {
    "id": "1842",
    "type": "Execution"
  }

to something like this:

  "dataSource": {
    "id": "visitor_visitation",
    "type": "Insights data"
  }

so, the idea is that the widget config itself is generic therefore widget 100084 can be used in the same dashboard for all dealers -- InsightsDataProvider and firstorder take care of adding the dynamic aspects (attaching the month/year and dealer ID).

[github-actions[bot]]

📚 Storybook preview (updated to 38599a75c23195bf4502998ba510364e8748781a)

[geoerika]

Nice work! As usual!