fix: swallow TCC.db SQL non-fatal warnings and log user friendly message

[cmorten]

Issue

Fixes #61

Details

When running npx @guidepup/setup setup locally it is generally expected that TCC.db updates will be denied due to SIP (generally a good thing!).

For local development this isn't really a problem because when it comes to running Guidepup you will receive a system dialog prompting for permissions to automate applications (same as you get when using Playwright, or indeed many applications) which you can interact with to manually/JIT provide the required permissions.

Thus swallowing the stdout/stderr warnings that are emitted from the SQL command when it fails.

There is a risk that users will deny those permissions if they aren't aware why the dialog has appeared, so this change also adds a note log to explain the behaviour, linking off to docs for manual steps if preferred (or to rectify a denial of permissions from system prompt).

$ npx @guidepup/setup setup

[!] Note: Unable to configure automation permissions

This can be expected when running the Guidepup setup locally if macOS does not grant the required permissions automatically.
Please accept any system dialogs requesting automation permissions while using Guidepup.
If you are running Guidepup in CI, use the `--ci` option to skip interactive permission setup.
Alternatively, please refer to https://www.guidepup.dev/docs/guides/manual-voiceover-setup for instructions on manually configuring VoiceOver permissions.


Environment setup complete 🎉

CheckList

• Has been tested (where required).