(Accessibility)(Meta) Track nested-interactive axe-core violations in product UI so we can re-enable the rule

[1Copenut]

Description
@bhavyarm is working to bump our axe-core to a more current version in #144940 and has been running into a number of nested-interactive violations. We opted to ignore the nested-interactive rule temporarily to get the benefit of other new rulesets, with the understanding we do want to fix the identified violations. Opening this meta issue to track those so they can be assigned to product teams and added to future roadmaps.

Actual Result

• Buildkite shows a number of unique nested-interactive element violations

Expected Result

• Buildkite shows 0 nested-interactive-element violations when the rule is re-enabled

Relevant WCAG Criteria:
SC 4.1.2: Name, Role, Value (Level A)

• A11y violation for Ensures interactive controls are not nested as they are not always announced by screen readers or can cause focus problems for assistive technologies on dashboard controls #154296
• Interactive controls must not be nested a11y error for waffle chart suggestion on create lens viz page #154787
• Interactive controls are not nested a11y violation on uptime Accessibility overview alert popover controls #154788

[elasticmachine]

Pinging @elastic/kibana-accessibility (Project:Accessibility)

[elasticmachine]

Pinging @elastic/kibana-qa (Team:QA)

[alexwizp]

I see all linked issues were closed, this meta issue looks obsolete