dterm: add caveat and uninstall

[L2G]

This adds a caveats stanza to highlight the need for accessibility permissions and an uninstall stanza to quit the app upon removal.

[vitorgalvao]

Pinging @rolandwalker, @ndr-qef, and @claui (since you’ve expressed interested in UX).

Bringing this up since it looks like @L2G might be submitting more PRs of this form (apologies for hijacking your PR for this discussion). uninstall :quit isn’t required here, but it does make sense and can go a long way towards user perception of our care towards casks (“wow, they’ve even closed it for me”). I definitely like it, and while I’m not suggesting it should become mandatory, I’d like to know if you’d agree with encouraging it in the documentation.

[rolandwalker]

We've had the ability to do uninstall :quit there since #4865, and it was intentionally added, so we might as well play with it to see what end-users think.

However, now that we have the app stanza, we can add app-specific logic on the backend that finds the bundle ID at runtime and operates on it implicitly as in #7854. So, at this point we could make all app Casks consistently (and implicitly) quit the app if running at uninstall time, if that was desired.

Running in the opposite direction, we are adding uninstall :trash, which is only a stub, but which when implemented would allow most app bundles to safely continue running after uninstall.

@L2G you've caught me right in the middle of removing the assistive_devices method (#7855), which will become a renamed toplevel stanza in the next release per #7854. The best way to roll with the transition is to write out the caveats literally and leave a todo comment as in plover.rb

[vitorgalvao]

Thank you for the contribution, @L2G. It will be merged in a different pull request due to some simple recommended alterations. Your contribution is still included (and still credited to you), with the appropriate modifications, when applicable.

Changes:

• Mentioned accessibility_access change.

[L2G]

Sounds good.