Termux plugin support

[ksh-b]

This would allow easer to run commands via termux

Changes required in easer:

• Permission in easer: com.termux.permission.RUN_COMMAND
• Preferably a new skill to enter command path, arguments, etc

I made changes in termux properties file, added the above permission in easer, and entered the following via 'Run commands' skill:

am startservice --user 0 -n com.termux/com.termux.app.RunCommandService \
-a com.termux.RUN_COMMAND \
--es com.termux.RUN_COMMAND_PATH '/data/data/com.termux/files/usr/bin/top' \
--esa com.termux.RUN_COMMAND_ARGUMENTS '-n,5' \
--es com.termux.RUN_COMMAND_WORKDIR '/data/data/com.termux/files/home' \
--ez com.termux.RUN_COMMAND_BACKGROUND 'false' \
--es com.termux.RUN_COMMAND_SESSION_ACTION '0'

Works fine. But if we could have an UI for adding command path, arguments and the other options it would be nice, so that user doesnt have to enter the whole command.

[Para-lyzed]

@renyuneyun Could the Manifest be updated to request the com.termux.permission.RUN_COMMAND permission in the next released version so we can use Termux without having to build the app ourselves with our own Manifest? Even just using it via the am startservice command mentioned above works for a temporary fix to this multi-year issue, many other users have wanted to use Termux with Easer, and it's been completely preventing me (and others) from switching to Easer for well over a year (see #205). I understand being busy, but it's just a single line in a single file that would need to be changed.