Handle resume correctly (with Oxide and other launchers)

[fenollp]

cc #6
and https://oxide.eeems.codes/documentation.html

[Eeems]

The simplest way would be to just handle SIGCONT, as that signal is sent when a process is resumed after being paused. You won't be able to handle the signal sent to pause the application, which means you can't do any sort of clean up before pausing.

Oxide has an alternative application mode that will use SIGUSR1 and SIGUSR2 signals that need to be acked back to tarnish for suspend/resume.

• Under type look at backgroundable: https://oxide.eeems.codes/documentation/03_application_registration_format.html
• You'll need the PID for tarnish, that you can get with tarnishPid: https://oxide.eeems.codes/documentation/api/01_general.html