Add local test environment configuration (via Docker Compose / Drupal VM)

So, to be honest, one of the main reasons I am often hesitant to dive in and test/commit a patch in this issue queue is the length of time it takes me to go from "look at issue in issue queue" to "have patch running in local environment".

What I currently do is either take an existing Drupal 8 instance running via Drupal VM and toss Honeypot in there to test, or use Drush to build a new D8 site locally. Either way takes at least a couple minutes at best, or 10-20 minutes if I haven't been doing any Drupal work for a while. That's a lot of time when I often only have 20-30 minutes to dedicate to patch review in a given week! (Some months I devote a whole 2 hour slot though, so it's not as bothersome there).

With Drupal VM's recent addition of Docker compatibility, I've been starting to convert most of my personal side-projects (where I had the same problem as I have with this module) to use the Docker image and build on top of it (instead of building an entire new VM instance with Vagrant + VirtualBox).

I've opened an upstream issue to help with this (Add documentation on using Drupal VM for quick module/project demo environments via Docker), but basically, I would be able to just add a docker-compose.yml file and some instructions for bringing it up in the module README, and I'd have a one-off local environment I could use for testing, which could be built in 10-20 seconds (and then add another 30s or so for a Drush site-install to run).

Much more convenient, and I may also be able to add in a script or a couple Docker commands in a Dockerfile that puts the Honeypot module in the right place and enables it...