prefix all messages (event error messages) with check on quiet

[tomeichlersmith]

This resolves #139 by silencing all¹ messages when the user requests --quiet. I think there are some updates to the init recipe in the ldmx-sw justfile that are important as well, but this at least avoids the confusing error message being printed when a normal situation occurs.

Namely

if ! denv check --workspace --quiet; then
  denv init owner/repo:tag
fi

can quietly insure that a workspace has been initialized in scripts.

Leaving this as draft while I think about if there is a better solution. Maybe a flag to denv init can encompass the above code in scripts in a more clear manner. 🤔

Footnotes

1. Except the CL parsing error message which doesn't know if the user wants --quiet or not yet. ↩

[tomeichlersmith]

Just brainstorming.

There are two decisions a user has to make when running denv init. Whether to overwrite/override an existing denv and whether to create WORKSPACE if it doesn't exist yet. We could have these decision made on the CL so that script-writers could avoid prompts and we could have these separate so that script writers could silently avoid re-initializing by simply passing a CL flag.
This complicates the denv init CL but keeps denv check something that users would do as a debugging measure.

I think a full CL implementation would involve four new flags.

--[no-]over  : Don't ask about overwrite/override. Instead just do it (--over) or don't do it (--no-over).
--[no-]mkdir : Don't ask about creating WORKSPACE if it doesn't exist. Instead just do it (--mkdir) or don't (--no-mkdir).

And --force would become an alias for --over --mkdir.