feat(icon): icon component migration

[ashley-hunter]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our
  guidelines: https://github.com/goetzrobin/spartan/blob/main/CONTRIBUTING.md#-commit-message-guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

Which package are you modifying?

• accordion
• alert
• alert-dialog
• aspect-ratio
• avatar
• badge
• button
• calendar
• card
• checkbox
• collapsible
• combobox
• command
• context-menu
• data-table
• date-picker
• dialog
• dropdown-menu
• hover-card
• icon
• input
• label
• menubar
• navigation-menu
• pagination
• popover
• progress
• radio-group
• scroll-area
• select
• separator
• sheet
• skeleton
• slider
• sonner
• spinner
• switch
• table
• tabs
• textarea
• toast
• toggle
• tooltip
• typography

What is the current behavior?

Currently we wrap the NgIcon component which adds a hard dependency on the library and more specifically can lead to us being tied to a specific version and make it hard to update if there are ever any breaking changes.

This pull request changes the component we had to a directive that applies the little bit of custom styling we add, this removes the hard dependency on any specific version of NgIcons.

What is the new behavior?

We use the ng-icon component directly and add an attribute for the styling

Does this PR introduce a breaking change?

• Yes
• No

Other information

I have added an automated migration to assist in the process of migration as this is a breaking change