[Emotion] Delete distributed *.css files

[cee-chen]

Summary

Our compiled/exported dist/*.css files no longer contain any meaningful CSS, just @keyframes animations that have zero usage in Kibana. We should go ahead and remove the file(s) fully at this point.

Before	After

Pending PRs:

• Delete imports/references to EUI's distributed .css files kibana#194082 (failed)
• Delete imports/references to EUI's distributed .css files kibana#194237
• https://github.com/elastic/cloud/pull/132101

QA

N/A, if CI/yarn build-pack passes, we should be set

General checklist

• Browser QA - N/A
• Docs site QA - N/A, already handled in [Docs] Update references to Sass/Emotion migration #8029
• Code quality checklist - N/A
• Release checklist
  • A changelog entry exists and is marked appropriately.
  • If applicable, added the breaking change issue label (and filled out the breaking change checklist)
• Designer checklist - N/A

[github-actions]

This PR contains breaking changes. The opener of this pull request is asked to perform the following due diligence steps below, to assist EUI in our next Kibana upgrade:

• If this PR contains prop/API changes:
  • Search through Kibana for <EuiComponent usages (example search)
  • In the PR description or in a PR comment, include a count or list with the number of component usages in Kibana that will need to be updated (if that amount is "none", include that information as well)
• If this PR contains CSS changes:
  • Search through Kibana for the changed EUI selectors, e.g. .euiComponent (example search)
  • In the PR description or in a PR comment, include a count or list with the number of custom CSS overrides in Kibana that will need to be updated (if that amount is "none", include that information as well)
• 🔍 Tip: When searching through Kibana, consider excluding **/target, **/*.snap, **/*.storyshot files to reduce noise and only look at source code usages
• ⚠️ For extremely risky changes, the EUI team should potentially consider the following precautions:
  • Using a pre-release release candidate to test Kibana CI ahead of time
  • Using kibana-a-la-carte for manual QA, and to give other Kibana teams a staging server to quickly test against

Log | Bot Usage

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 8146c37

[mgadewoll]

🚢 🐈‍⬛ LGTM!