Now that we have the concept of Advisories to provide general-purpose
information about packages, we should try and simplify the reporting
output for End-of-Life data queries, too.

This can be done by creating a - complex - query that `JOIN`s between
the End-Of-Life tables, and the `advisories` table with a `UNION`, and
coerce the End-of-Life formats into the form that we'd be expecting
Advisories to be in.

We need to introduce `queries_hack` to allow us to work around
https://github.com/kyleconroy/sqlc/issues/1546 to provide `UNION`
support across tables.

This also includes slightly more information in the queries, detailing
the `platform` and `organisation`, and merges the `current_version` into
the `version` column.

Unfortunately there's not a great way of deduplicating the data checking
(via `julianday`) and adding an intermediate variable, so it's very
duplicated.

This also hardcodes the `60` day lifetime for deprecation window.

As we're now able to report this directly from
`advisories.ReportRenovate` we can remove the `endoflifedate.Report`
functionality.

Closes #116.