As a means to allow us to centrally control the way that we open the
database, as well as allowing us to modify the querystring in a central
place in the future, or apply further checks.

To allow for easier debugging when we see errors or warnings, we can
pre-populate the version of `dmd` into the output.

As it is the CLI version that was used to create the database, not the
currently running CLI version.

Add table for managing "sensitive" package names

Closes #189

See merge request !133

To make it clearer to the user that they are (not) using sensitive
packages, we can add a log message when about to process the data.

And link it through from the CLIs that mention this may be leaking data.

As noted in #189, there's no way right now to avoid leaking internal
package names to the public Internet when generating advisories or
missing data.

Right now, the solution is to just deal with it, which isn't ideal.
Instead, we can add this as a first-class citizen with a new table, and
the ability to ignore these packages when performing lookups.

This requires we tweak our existing queries to now left join (in case
there's no match) the `sensitive_packages` table and filter out/in
packages as appropriate.

Closes #189.

Update module github.com/deepmap/oapi-codegen to v1.16.2

See merge request !134

Check for broken links in the pipeline

See merge request !132

As a way to ensure that we don't end up with broken links - like we
previously had - we can utilise a Netlify build plugin to make it easier
to validate this.

Which addresses broken URLs.

Due to [0], and fixes several broken links.

[0]: https://www.jvt.me/posts/2019/11/11/gotcha-netlify-lowercase/

Add Getting Started cookbook for SBOMs

See merge request !131

Update github.com/saschagrunert/demo digest to 5fce153, run Go 1.21 in demos, and use `sh` for demos

See merge request !126

As we've now added upstream functionality to override this, we can
remove the reliance on `bash`.

Overhaul + improve documentation site

Closes #198, #154, and #178

See merge request !130

This is a rather large change, and I'd rather not try and break it down
into multiple commits, so here we are.

We want to:

- Add a Concepts section to describe each of the key building blocks
- Add a Cookbooks section to provide common guides
- Add a flowchart for "which tool should I use"
- Add a document on how to deploy the infra
- Migrate the getting started guide from my blog[0]
- Restructure the menu to better fit the new structure
- Reduce some of the content on the homepage

Closes #178, #154, #198.

[0]: https://www.jvt.me/posts/2023/07/25/dmd-getting-started/

Add explicit content licensing to site + update /features/

See merge request !129

As per a discussion in
#167 (comment 1606587809)

As it makes it clearer to read.

Add link to talk video

See merge request !127

Add `db generate missing-data` command

Closes #148

See merge request !125

As part of #77.

As part of #77, we proposed to add support for integration with
`deps.dev` to look up package dependencies.

To do this, we can add support for the `GetDependencies` endpoint on our
`depsdev.Client`, and look up each dependency's dependency tree.

This requires we introduce two new queries to Renovate + SBOMs to be
able to query the existing data, including the full repo + ecosystem
data.

We can copy-paste the existing `Generate` functionality and tweak it to
work for the dependency lookup.

We make sure to trim down the requests we're sending with Renovate data
as there's a lot of data that fails to be looked up without doing so.

For now we can add support for the Maven ecosystem which appears to be
the biggest concern, as Renovate nor SBOM exports we've got include the
full dependency tree.

Co-authored-by: Jamie Tanna <jamie.tanna@elastic.co>