denv passing through init even though deduced config is different from requested init

[tomeichlersmith]

Describe the bug
denv doesn't complain when init is run that would require overwriting but is instructed to not overwrite.
The problem here is not that denv refuses to over{write,ride}, its that the user is not told that the skipping is done.

To Reproduce

tom@zuko:/tmp/tmp.uZFZubM2sH$ denv init alpine:3.19
tom@zuko:/tmp/tmp.uZFZubM2sH$ mkdir subdir
tom@zuko:/tmp/tmp.uZFZubM2sH$ cd subdir
tom@zuko:/tmp/tmp.uZFZubM2sH/subdir$ denv init --no-over alpine:3.20 /tmp/tmp.uZFZubM2sH/subdir
tom@zuko:/tmp/tmp.uZFZubM2sH/subdir$ denv config print 
denv_workspace="/tmp/tmp.uZFZubM2sH"
denv_name="tmp.uZFZubM2sH"
denv_image="alpine:3.19"
denv_mounts=""
denv_shell="/bin/bash -i"
denv_network="true"
podman version 3.4.4

Expected behavior
I would like denv to fail when running denv init --no-over --no-mkdir owner/repo:tag /full/path/to/workspace if the deduced already-existent denv is not /full/path/to/workspace.

Additional context
LDMX-Software/ldmx-sw#1472 (comment)

[tomeichlersmith]

Ended up being easier than I was worried about, resolved by 5c3766b