[BUG] Skills failing to load due to issues in setup.py do not log exceptions

When developing skills and experimenting with different packaging, or with the projen skill generator, sometimes I'll make changes to setup.py to test something and fail. When this happens my skill fails to load but doesn't give me anything in the OVOS logs as to why. I do get those logs when I pop a REPL and instantiate my skill class (or do it in my IDE).

This leads to a poor developer experience, as it's not intuitive at all for someone unfamiliar with how OVOS handles skill loading. Acceptance criteria would be logging those exceptions in OVOS when a skill fails to load properly.

[JarbasAI]
LOG.exception will print them
probably somewhere in the loading of skills isnt doing this and should

Start by tracing the skill-loading path in ovos-plugin-manager and reproduce a load failure caused by an invalid setup.py. Compare this with instantiating the skill in a REPL, where the exception is visible, and identify where LOG.exception is missing. Done means setup.py-related skill-load exceptions appear in the OVOS logs.