[Feature Request] Inform user if fontawesome.com has bad TLS cert when pulling UI assets / Ensure software remains functional if UI assets are unable to be downloaded.

[vyressi]

Generate user-facing error message when firebot is unable to download assets from fontawesome.com due to TLS or firewall issues.

Allow/Enable software to continue to function without these remote assets until the issue can be corrected.

Alternately give user a choice to ignore TLS issues for asset download at their own risk.

Alternately: Have default local assets that are not cached to fall back on.

Additional context There was a brief period on 18/7/22 where kit.fontawesome.com had an incorrect SSL certificate. While this issue is outside firebot's purview, the only indication that there were any connection issues was a single line item in the console of developer mode, something that most end users wouldn't be able to identify.

Furthermore, when firebot was unable to obtain its assets, the program wasn't usable with functional, if undesirably blank buttons. Much of the UI broke and buttons became completely nonfunctional, most notably the 'connect to twitch chat' slider element.

[SReject]

Context: Due to client-side system configurations for the user, Firebot failed to load FA assets. When this happens, Firebot's UI is mostly unusable. This is a feature request to gracefully handle FA assets failing to load.

[TheBlackParrot]

csshake is causing me some problems this morning, although this is just a complete timeout. relevant to that last part of the issue title, firebot refused to load for a good bit