Pass verbosity level to conda-build, otherwise very hard to debug

[corneliusroemer]

I got stuck debugging a bioconda-utils build failure and was surprised that passing --loglevel debug had no impact on the log level of the subcommand conda-build that was run.

To me this appears to be a clear omission that ought to be fixed by passing log level through to relevant, if not all, subcommands that are called by bioconda-utils build.

I think one could add it here to the args for example:

bioconda-utils/bioconda_utils/build.py

Lines 150 to 155 in a5882cc

	conda_build_cmd = [utils.bin_for('conda-build')]
	# - Temporarily reset os.environ to avoid leaking env vars
	# - Also pass filtered env to run()
	# - Point conda-build to meta.yaml, to avoid building subdirs
	with utils.sandboxed_env(whitelisted_env):
	cmd = conda_build_cmd + args

See https://matrix.to/#/!MhHkICgthNLZeLiygG:gitter.im/$WeOBUkiNJp1cTuQXp7mOPmZWFqFmO4w5TETB-flZu0k?via=gitter.im&via=matrix.org&via=one.ems.host for context