[Maps] Add filter actions to tooltips

[thomasneirynck]

Closes #32736

This PR contains:

Refactors

• creates typing for individual tooltip-properties

Changes/additions

• use grid layout for tooltips
• show filter actions only in read-only mode (ie. when embedded in dashboard)
• add phrase filtering for any string property on any ES-source
• add phrase filtering for any property that is joined to other ES-sources (e.g. EMS layer)

Known issues:

• joined data on the map does not update based on changing filters (regardless if the filter is sent from the map, or from another visualization)

Other todos:

• add functional tests for tooltips use jest tests for contents
• detect presence of filter-bar iso using isReadOnly embeddables are always filterable right now
• design (it needs it!)
  • do not show close button when hovering
  • do not show filters when hovering
  • change to + icon for filter creation button
  • change mouse-pointer when tooltip is "lockable" on click

Discuss:

• should the map take "ownership" of filters (similar to the input controls visualization) (?) NO. maybe in another phase
• should tooltips remain on the map after filtering (?) if so, what would be the best mechanism to introduce this (e.g. track doc-ids across data-updates. (?) NO. tackle this as separate improvement. right now, tooltips are removed after filtering

---

[elasticmachine]

Pinging @elastic/kibana-gis

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request

[elasticmachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request

[elasticmachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request

[elasticmachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request

[elasticmachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request

[nreese]

Instead of recreating the array on each iteration, how about something more like this?

  async getPropertiesForTooltip(properties) {
    const sourceTooltipProperties =  await this._source.filterAndFormatPropertiesToHtml(properties);
    this._addJoinsToSourceTooltips(sourceTooltipProperties);

    // tooltip properties added by joins. For example, aggregation metrics
    const joinTooltipProperties = [];
    for (let i = 0; i < this._joins.length; i++) {
      const propsFromJoin = await this._joins[i].filterAndFormatPropertiesForTooltip(properties);
      joinTooltipProperties.push(...propsFromJoin);
    }
    return [...sourceTooltipProperties, ...joinTooltipProperties];
  }

[nreese]

lgtm
code review, tested in chrome