(BOLT-1303) Initial work to add a `puppet-bolt` docker container

[underscorgan]

This uses the same tooling / pattern as the puppet-agent-ubuntu container. Would eventually want this set up in jenkins I think, but the pipelines config was trivial to copy over so I stuck with that for now.

Still todo:

• [x] Is this a reasonable command to run?
• [x] what volume mounts do we need?
• [x] do we need to copy over any configs?
• [x] other ENV variables to expose in the container / bolt config?
• [x] more thorough testing (blocked on better understanding of how the container will be used)
• [x] container docs

[donoghuc]

@underscorgan we did not get to discuss this ticket at planning this week. I will move it to top grooming.

[donoghuc]

Is this a reasonable command to run? I think so :) what volume mounts do we need? Can we let consumers just set them? do we need to copy over any configs? Again, let consumers do it other ENV variables to expose in the container / bolt config? I think we currently only support BOLT_INVENTORY which seems like we can just document it more thorough testing (blocked on better understanding of how the container will be used) If we stick with just installing the bolt packages on an ubuntu base image i dont think we will need much testing. container docs Going to add a draft in this PR

I added a commit documenting what we have here. I think we should keep this as simple as possible for now. Also we created a separate ticket to track automation of publishing/testing.

[nicklewis]

$ docker run --name bolto -v /var/run/docker.sock:/var/run/docker.sock puppet-bolt command run -n docker://bolto 'echo hello world'
Started on bolto...
Finished on bolto:
  STDOUT:
    hello world
Successful on 1 node: docker://bolto
Ran on 1 node in 0.17 seconds

I love it.