acronis-true-image 41592: improve uninstall and implement zap

[unshare]

Uses acronis-true-image-cleanup-tool

Important: Do not tick a checkbox if you haven’t performed its action. Honesty is indispensable for a smooth review process.

In the following questions <cask> is the token of the cask you're submitting.

After making any changes to a cask, existing or new, verify:

• The submission is for a stable version or documented exception.
• brew audit --cask --online <cask> is error-free.
• brew style --fix <cask> reports no offenses.

Additionally, if adding a new cask:

• Named the cask according to the token reference.
• Checked the cask was not already refused (add your cask's name to the end of the search field).
• brew audit --cask --new <cask> worked successfully.
• HOMEBREW_NO_INSTALL_FROM_API=1 brew install --cask <cask> worked successfully.
• brew uninstall --cask <cask> worked successfully.

---

[daeho-ro]

What is the reason to depends on acronis-true-image-cleanup-tool cask?

[unshare]

What is the reason to depends on acronis-true-image-cleanup-tool cask?

The cleanup tool is downloaded separately from a different location.
It is the ultimate cleanup tool most suitable for the zap and it is maintained by the upstream vendor.
For cleanup tool to be available at the zap time, it's declared as a dependency of the main application cask.

[unshare]

Updated to resolve conflicts with others' efforts to implement uninstall + zap.
The procedure proposed here is much more robust and it uses vendor-supplied tool for this specific purpose.

[unshare]

@daeho-ro Will anyone review this?

[bevanjkay]

Is it necessary to call these IDs in three separate places?
Currently with uninstall quit, and then TERM and KILL in the signal stanza.