ci: init GitHub Actions CI for Keto

[icyphox]

This PR introduces a GitHub Actions workflow for CI. There are no new secrets required for this workflow. As always, remember to create an environment production from the repo settings.

Related issue(s)

Checklist

• I have read the contributing guidelines.
• I have referenced an issue containing the design document if my change
  introduces a new feature.
• I am following the
  contributing code guidelines.
• I have read the security policy.
• I confirm that this pull request does not address a security
  vulnerability. If this pull request addresses a security. vulnerability, I
  confirm that I got green light (please contact
  security@ory.sh) from the maintainers to push
  the changes.
• I have added tests that prove my fix is effective or that my feature
  works.
• I have added or changed the documentation.

[CLAassistant]

All committers have signed the CLA.

[icyphox]

P.S. the first autogen commit was from CircleCI.

[zepatrik]

Why is this not a service like postgres and mysql? Just asking out of curiosity.

[icyphox]

GitHub, it appears, like to release half-baked features — service containers don't support overriding the default entrypoint command, or even passing args to them. And with Cockroach, we'd like to run it with the start-single-node --insecure args, and this isn't possible with service containers. So back to the old fashioned way of spinning up a container in the background, by hand. :P

[zepatrik]

Haha ok, makes sense.

[aeneasr]

@icyphox isn't this missing - similar to Ory Hydra - the post-release step with the docs building stuff?

[icyphox]

@aeneasr that's already baked into the ory/ci/releaser action. No further setup required.

[aeneasr]

😎