feature: Improve logging of unhandled exceptions in taps/targets

[WillDaSilva]

Feature scope

CLI (options, error messages, logging, etc.)

Description

Original Slack thread (private channel): https://meltano.slack.com/archives/C01V5RPLLN4/p1660633635134939

For context, this tweet identified a longstanding issue where taps and targets that do not use our SDK may have uncaught exceptions that are printed to stderr, then propagated to Meltano at the INFO log level, which leads to log output like this:

To handle these cases generally without requiring the extensions use our SDK (and by extension, structured logging), we may be able to override sys.excepthook in their Python processes to communicate the exception back to Meltano, where it can be logged in an appropriate manner.

[stale]

This has been marked as stale because it is unassigned, and has not had recent activity. It will be closed after 21 days if no further activity occurs. If this should never go stale, please add the evergreen label, or request that it be added.