Fixes #1

corrected the path for the default rulesets file inside the archive
additionally provide a new error that gets thrown when the appropriate
file has not been found inside the downloaded archive

could → couldn't

update: add debugmessages

when a ruleset file was empty, the json parser tried to parse it
and failed. now we check wheter the file is 0 bytes long and disqualify
it if so. now the most severe message that will be shown is a warning

in the scope of the application that uses libhttpseverywhere
it's not necessarily critical

TODO: think about letting the programmer decide wheter he
wants libhttpseverywhere to fail critically or not

only load the rulesets from $sourcedir/data/default.rulesets when
we are executing httpseverywhere_test from a folder that ends with
"build/test", which is the folder that meson creates for our test
executable. this will prevent loading random crap data in production

was broken after splitting meson.build in one file per
sub folder

each folder now has its own meson file

  * we now display a repology badge to demonstrate where
    our package has found a home in
  * clearer instructions about building docs

in the new HTTPSEverywhere-Packages the rulesets reside
in a different folder under a different name. The updater now
takes this into account

and deprecated ignore by id