GitHub Pages -> Lambda SSR?

[randytarampi]

I've always wanted to do this, but was always concerned with cost.

Per my note in #77, that's probably a terrible reason not to do this.

What makes this a bit more challenging is that we'd need to chase a few things down and deal with to make this work well.

1. Where do we serve assets from?
2. Do we want a versioned CDN, or will GitHub pages still suffice?
3. What kind of page load times are acceptable?
4. What kind of processing times are acceptable?
5. What kind of (dollar) costs are acceptable?
6. How do I transition from GitHub pages to Lambda (or equivalent) with 0 downtime?
7. How do I want to integrate this with posts.randytarampi.ca? With service.randytarampi.ca?

• How this relates with posts.randytarampi.ca -> service.randytarampi.ca #164 is a pretty big question. I'd like to have a lambda to serve at www.randytarampi.ca, but don't really want to have to split out some @randy.tarampi/serverless utility library.