Generate ublock.sqlite patterns file from scratch during build time

Currently we convert a raw text dump of the ublock.sqlite database (which contains settings and patterns for the uBlock Origin Addon for Tor Browser) into the sqlite database blob during build time. This requires updating of the ublock0.sqlite from a running Tails, converting it into the dump and commit it into the repository before building Tails (see contribute/release_process.mdwn). config/chroot_local-hooks/12-generate-ublock-origin-filter will convert the dump into the needed sqlite blob during build time.

From https://labs.riseup.net/code/issues/9833#note-25:

Regarding what uBO needs in the SQL database depends on what are the specific settings you wish to be different than the ones set by default.

We could also decide to not ship any filter lists (in this case, this would save us work and make the repo/iso a few MBytes smaller, but apparently it takes some minutes after starting the browser until the download of filter lists will start):

Normally it should not be necessary to include the content of filter lists in the SQL file, as uBO will fetch the content of the enabled filter list(s) from their remote location(s) or the local installation (assets/thirdparties/). Some minutes after uBO is launched, it will update the enabled filter lists if needed, and their content will then be saved in the SQL database

Related issues

• Related to #9833 (closed)

Original created by @spriver on 12153 (Redmine)