Use --quiet --quiet by default for om ci and om show

[shivaraj-bh]

resolves #300

[shivaraj-bh]

I just realised, om ci might not need it yet, because devour_flake.rs pipes both stdout and stderr

omnix/crates/nixci/src/nix/devour_flake.rs

Line 77 in be6ce4a

let mut output_fut = cmd.stdout(Stdio::piped()).stderr(Stdio::piped()).spawn()?;

Edit: It will be useful during nix flake check when this case is hit:

omnix/crates/nixci/src/step/flake_check.rs

Lines 37 to 39 in be6ce4a

	for (k, v) in &subflake.override_inputs {
	args.extend(["--override-input", k, v]);
	}

[srid]

In [what] situations do we need this done for om show?

[shivaraj-bh]

In situations do we need this done for om show?

When nix_eval is called trying to fetch flake schemas:

omnix/crates/nix_rs/src/flake/schema.rs

Line 84 in be6ce4a

let v = nix_eval::<Self>(nix_cmd, &flake_opts, &inspect_flake).await?;

[shivaraj-bh]

On a second thought, it would be more appropriate to localise modifying NixCmd with --quiet --quiet right before where it is needed.

[srid]

In [what] situations do we need this done for om show?

When nix_eval is called trying to fetch flake schemas:

Not sure I understand. I don't see any override input relate logs when running, for example,

[shivaraj-bh]

The logs from --override-input are not shown in om show because we add --quiet --quiet by default in nix_eval. This PR allows to append --quiet --quiet directly to the NixCmd, instead of being specific to nix_eval and thus expanding the scope to use it in NixCmd used during om ci.