Continue in the face of failure

[KuleRucket]

Description

Instead of exiting when one of the major components fails to initialise, this change will log errors and continue. The advantage of this is that even though sunshine will not work, the web UI will still be available to view the logs and fix configuration.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Dependency update (updates to dependencies)
• Documentation update (changes to documentation)
• Repository update (changes to repository files, e.g. .github/...)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated the in code docstring/documentation-blocks for new or existing methods/components

Branch Updates

LizardByte requires that branches be up-to-date before merging. This means that after any PR is merged, this branch
must be updated before it can be merged. You must also
Allow edits from maintainers.

• I want maintainers to keep my branch updated

[KuleRucket]

This broke audio for windows because it is calling the deconstructor which deallocates the COM API used for audio.

This is currently impacting stable release.

I put the guard back in on this branch. Not sure if it needs to be a new PR though