Overhauled the system to be flexible enough to take local pro files or the site

[daemedeor]

Due to 6.2.0 release of Font Awesome, they overhauled the naming system that was in use and deviates a lot from the current cheatsheet version of the site. Since the enums are missing a lot from the pro versions and can no longer support the amount of Icons, I decided to overhaul the system instead. I know there are a lot of files changed but there wasn't a simple way to preserve the formatting of forced strings due to the complexity of the new structure.

I was missing a lot of icons between Feb 2022 and Sept 2022 version of Font Awesome, so this brings it parity. This also allows for people to feed their own version of FA in order to generate font files outside of the runs of this repo (which are few and far between).

[daemedeor]

Also note: this includes #67 as part of the request to merge. Would appreciate a look at it when you get a chance!

[klousy92]

You didn't add CaseIterable to the enums right?

So using the FontAwesome unicodes is still not possible with your changes?
Like this:

Awesome.Regular(rawValue: "\u{f007}")?.image

[daemedeor]

@klousy92 I had difficulties when I made it CaseIterable but I can try to make it work again. While you couldn't use Awesome.Regular(rawValue: "") unfotunately. But I did make a unicode exnteion in unicodeString OR you can do do Awesome.Regular.withKey(_) to find it that way

[jordanpwood]

@daemedeor, I tried forking off your repo and using the generator script to update to Awesome 6.4.0, but I don't know how to feed my local Pro files into the generator script. Can you give some guidance on how to do that?