New option "excludes" to provide a file with stacktraces that should be ignored


_This rebases changes from pull #10 onto the latest master as there are a number of conflicts otherwise._

When using file-leak-detector in ci, there are often many cases where the file-open is ok, e.g. third-party-code which cannot be changed or code where certain files are open for a long time, e.g. database-connections or log-files.

This patch adds an option "excludes=FILE", which can be used to specify a list of stack-trace-lines which denote file-opens which can be ignored and thus do not appear in the dumps.

If these excludes are done properly, I can then add a check in CI after the tests which ensures that the dump does not contain any entry at all, causing testing to fail as soon as new unclosed file-opens are added.