Add guided apply-to-system step after export

[cch1rag]

What problem does this solve in your TCC permission workflow?
After exporting a modified database, the final step of copying it back into place is manual and error-prone. Users have to remember the correct cp command, handle spaces in paths, and be careful about the source filename.

What behaviour do you want?
Add a post-export action that helps apply the modified database back to the user’s TCC location.

Possible behaviours:

• copy the exact cp command to clipboard
• open Terminal with a prefilled command
• optionally run the documented copy step after an explicit confirmation prompt

The flow should warn users to quit affected apps first and clearly explain risks.

Why does this fit a local macOS TCC editor instead of a system tool or third-party service?
This request is about reducing friction in the existing local handoff workflow after Clearance has already produced a modified database.

Scope check
As written, automatically copying into a live TCC location is not currently in scope under CONTRIBUTING.md, which says the project should not write to system TCC files.

This issue should therefore be treated as one of:

• a scope discussion for maintainers, or
• a narrower in-scope version that only generates/copies the command without executing it

Additional context
If this is pursued in any form, the UI should:

• reference the actual exported _modified.db filename
• distinguish user TCC from system TCC cases
• require an explicit confirmation step before any execution