Add feedback to users of FlightIcon when icon name is not correct

[didoo]

📌 Summary

As follow-up of this Slack conversation I have created a small PR that adds a feedback for the consumers of FlightIcons if a non-existing icon name is provided.

Example of what a developer would see in the console:

🛠️ Detailed description

In this PR I have:

• updated the build step in the Flight icons pipeline , to add the generation of a "index" file with the list of all the Flight icon names
• updated the EmberFlightIcon component/addon to throw an error if a non-existing icon name is used
  • in doing so, I had to move ember-auto-import from devDependencies to dependencies (otherwise the import of the index file would not work; see https://github.com/ef4/ember-auto-import#usage-from-addons)
• updated the integration tests for EmberFlightIcon

---

👀 How to review

👉 Review by files changed

Reviewer's checklist:

• +1 Percy if applicable
• Confirm that PR has a changelog update via Changesets if needed

💬 Please consider using conventional comments when reviewing this PR.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated
hds-components	✅ Ready (Inspect)	Visit Preview	💬 Add your feedback	Sep 29, 2022 at 1:13PM (UTC)
hds-flight-website	✅ Ready (Inspect)	Visit Preview	💬 Add your feedback	Sep 29, 2022 at 1:13PM (UTC)

[changeset-bot]

🦋 Changeset detected

Latest commit: 55f38cb

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 3 packages

Name	Type
@hashicorp/flight-icons	Minor
@hashicorp/ember-flight-icons	Major
@hashicorp/design-system-components	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[MelSumner]

Question: do you need two separate change logs?

[didoo]

@MelSumner using the yarn changelog command, it was not clear (to me) how to apply different semver increments to the packages, so I kept it simple and run it twice (and this created two files). I don't think this should make a difference for changelog (@Dhaulagiri can you confirm this?)

[Dhaulagiri]

It should be possible to combine them via yarn changelog but in practice I don't think it'll make a difference: changesets will be able to figure it out similar to if these were part of completely separate changes.