fix: exclude EuiButtonEmpty from the @elastic/eui/no-unnamed-interactive-element rule.

[alexwizp]

This rule was originally introduced in #8973.

However, EuiButtonEmpty already receives meaningful content as a child, which effectively serves the purpose of a role or aria-label. Therefore, explicitly requiring an additional accessibility attribute is unnecessary in this case.

Example of using EuiButtonEmpty

 <EuiButtonEmpty
    color="text"
    onClick={handleCancelOnClick}
    data-test-subj="protectionUpdatesCancelButton"
    disabled={isUpdating}
  >
    <FormattedMessage
      id="xpack.securitySolution.endpoint.protectionUpdates.cancel"
      defaultMessage="Cancel"
    />
  </EuiButtonEmpty>

Tests

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: f66e33a
• Documentation website
• Storybook

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: f66e33a

[weronikaolejniczak]

Hey @alexwizp all looks good! 🟢 I agree that this makes sense.

And in a case where the content is not enough, the consumer can always define aria-label (but it's not imposed).

Thanks for remembering about the tests! I hope that we can update our CI soon to include them 😄