Use sqlite for key persistence

[danielemery]

In order to make the keys project become usable by anyone but me, the keys themselves need to be dynamic.
To keep the container as simple as possible this should be achieved with something like an sqlite database.
Endpoints that can add and delete the different resource types also need to be in scope of this ticket.

Likely this will be considered a breaking change version of keys as it fundamentally changes the project.

[danielemery]

https://docs.deno.com/runtime/manual/basics/connecting_to_databases/#connect-to-sqlite-with-the-wasm-optimized-module Looks like a good choice for implementation

[danielemery]

I've been considering that one of the nice features of keys at the moment is not needing to worry about data management at all (backups, persistence etc). I'm now leaning towards an alternative of providing keys to the container via a config file or environment variables rather than dealing with a stateful application.

[danielemery]

Replaced by #29