yay, an up-to-date prebuilt image!

this changes the provided compose file to be more in-line with what a user would likely expect (as opposed to having to clone the full repo to build the image locally). the instructions about how to build the image with a compose file in the readme are still valid in-case people still want to go that route

(thanks oyster.cafe!)

Lewis: May this revision serve well! <lu5a@proton.me>

Lewis: May this revision serve well! <lu5a@proton.me>

Lewis: May this revision serve well! <lu5a@proton.me>

1.24 -> 1.25

Not sure how the Docker Hub image rebuild works, but this is what I'm usually locally

`UID` and `GID` args can now be set during build,
so following the example command in the README should fix
[#2](https://tangled.sh/@tangled.sh/knot-docker/issues/2)
by providing a `UID` and `GID` that exist on the host
so that the directories owned by git in the container
can be bind mounted on the host.

I couldn't push or pull from any repositories
until I set `-git-dir` following the instructions in
[knot-hosting](https://tangled.sh/@tangled.sh/core/blob/master/docs/knot-hosting.md#repositories),
so this adds the `/etc/ssh/sshd_config.d/authorized_keys_command.conf` file to `rootfs`.

Not the most elegent solution, but it works™ and should be fine in a
container

bash is now necessary to run the knot post-receive hooks; see
https://tangled.sh/@tangled.sh/core/blob/master/hook/setup.go#L134

Otherwise gives an error of `invalid port specification: "133342"`

Signed-off-by: Anirudh Oppiliappan <anirudh@tangled.sh>