[Dashboard] New setting to filter only the relevant panels

[teresaalvarezsoler]

Problem:
When users use the global filters, query bar or the controls, the panels that are not built using the dataview or index return no results.

Solution:
Ad a new setting that allows panels to ignore the filters when they are built with a different index or dataview (exact wording TBD)

Requirements:

• Add a new setting to the dashboard setting
• This should work for filter pills, KQL and controls
• This should work for Lens, ESQL, Maps, Field Statistics, Saved Searches and Vega (ML and SLOs already seem to work this way)
• If Ignore filter(s) from Advanced Settings is ON, this setting will always be ON and disabled so users can't change it.
• Existing dashboards will have this setting OFF if the Ignore filter(s) from Advanced Settings is also OFF, otherwise turn it ON
• New dashboards will have this setting ON by default

Communicate to users:

• New users don't need any communication, they will get used to the new way of filtering as it is also the default in other tools and
• Existing users need some explanation and a way to change it if they want to:
  -- The first time an existing user filters a dashboard (in edit or view mode) that contains more than 1 dataview where this setting is ON, show a tour pointing to the filter pills
  -- In the tour, show a description of the change, a link to the dashboard settings and a checkbox "Don't show again"
  -- The tour should appear per user, i.e if another user opens the same dashboard, the tour will appear again

Question:

• Should this also apply to Lens when it uses different layers with different dataviews?

[elasticmachine]

Pinging @elastic/kibana-presentation (Team:Presentation)

[cqliu1]

We should timebox this and do some research into the implementation of this setting.

Things to research:

• Should this setting only apply to filter pills and controls, not queries? That is how the ignore filters advanced setting behaves as queries can be very complex.
• Can we filter out irrelevant filters at the embeddable level? This way dashboard can handle removing ignored filters instead of having to support this ignore filters setting in each embeddable type.