feat(clock): add Doomsday clock

[angrybacon]

This MR to save my progress on #36. Mostly a proof of concept for when the sharing issue described below is solved. When/if it does get solved, the idea is to have the current -- as per thebulletin.org -- Doomsday clock on the Wiki behind Konami.

Next.js does not yet support a way to reuse asynchronous data across multiple pages (see vercel/next.js#10949). The workaround is to rely on getStaticProps from _app.tsx and the caveat is that the data will be queried for every page built. Several ways exist to mitigate the issue, all imperfect:

• Cache the data using the pipeline memory through promise cookies like this MR currently proposes (see src/tools/clock/getClockCached.ts for the limitations)
• Cache the data using a file: requires running a secondary Node instance to read and write the file
• Run a fetching script before the Next.js build: requires a more customizable pipeline: currently not supported by Netlify's free plan
• Cache the data using a server. See scryfall/server.js