Add a blacklist for files that may cause issues to "AM"/"AppMan"

[ivan-hc]

fix #988

The cataloging of programs, daemons, libraries and services that could compromise the functioning of "AM" begins.

It often happens that some AppImage package manager in the form of a service or system daemon, takes control of such packages, preventing other managers, such as "AM", from being able to manage them as well.

For example, it could prevent the extraction of the package (to obtain the launcher and the icon), the cataloging of installed apps based on the format, even the updating of them. All this can appear in the form of error messages like this:

❯ appman install evince baobab-gtk3
============================================================================

                  START OF ALL INSTALLATION PROCESSES

============================================================================

 ◆ "EVINCE": starting installation script

Document-Viewer_46.3.1-2- 100%[===================================>]  55.69M  6.23MB/s    in 9.1s    
This doesn't look like a squashfs image.
Failed to open squashfs image
This doesn't look like a squashfs image.
Failed to open squashfs image
sed: can't read ./evince.desktop: No such file or directory
mv: cannot stat './evince.desktop': No such file or directory

 "EVINCE" INSTALLED (56 MB OF DISK SPACE)
____________________________________________________________________________

 ◆ "BAOBAB-GTK3": starting installation script

Disk_Usage_Analyzer-3.38. 100%[===================================>]   3.74M  3.83MB/s    in 1.0s    
This doesn't look like a squashfs image.
Failed to open squashfs image
This doesn't look like a squashfs image.
Failed to open squashfs image
sed: can't read ./baobab-gtk3.desktop: No such file or directory
mv: cannot stat './baobab-gtk3.desktop': No such file or directory

 "BAOBAB-GTK3" INSTALLED (4 MB OF DISK SPACE)
____________________________________________________________________________
============================================================================

and the user who doesn't know where the problem is, will blame the new AppImage manager for this failure.

We don't want this to happen again!

---

1. appimaged

The first blacklisted file is the program and system daemon "appimaged", guilty of recognizing all AppImage files in the system to integrate them, causing the addition of more entries in the application menu (sometimes broken and not well patched), and managing updates differently from the one supported by "AM", compromising its scheme.

From now on, its presence will be reported, preventing the use of "AM" and explaining the reason via message.

[ivan-hc]

2. appimagelauncherd

The reference is the system daemon "appimagelauncherd", common in all known packages (DEB, RPM and PKGBUILD) and a sign of a system-wide installation of AppImageLauncher. The damage caused by such an installation is bad for all alternative AppImage package helpers, not just for "AM"/"AppMan".

It is still suggested to use AppImageLauncher as a standalone AppImage package, also available in this database.

It is the only way to make AppImageLaucher coexist with other AppImage package managers without them conflicting, and without necessarily having to use root privileges to solve compatibility problems.

[ivan-hc]