Improve organization of issues and improve troubleshooting-scenario

[sundhaug92]

1. Enable users to label issues with labels such as "signature-request", "false-positive", "feature-request", "tech-support" and "bug-report"
2. Provide a guide for how to report and document issues. For example, the template for signature-requests should include atleast one example file, as well as context for the file (such as device specs). Examples should be provided for good-titles for issues of the various labels, "X blows up when Y", "Martians detected on Venus" and such.
3. Error-messages and suggestions should be a part of the program-output. For example, during installation:

 * Warning: recommended package python-lzma not found, ...
 * Suggested package X not found ...

, something like sundhaug92/binwalk@f6b8665 but less strict and capable of handling the various levels of "suggestiveness".

4. Some alerts might be helpful for experienced Linux/UNIX-users but less helpful for others. I therefore propose sundhaug92/binwalk@09a3f06 as an example, since it provides some idea about what the user can to to solve the underlying issue. This might also help with issues like Wiki describes --disasm option #229, depending on implementation.

5. Create an FAQ for frequently asked questions and issues.

[CoffeeExpress]

Sorry for the long reply window. I'm currently trying to clean up the binwalk issues and will take this under consideration.

Thanks!