Add 'verbose' option to package command

[sdassow]

This is picking up from fyne-io/fyne#3352 to fix fyne-io/fyne#3069.

It passes the verbose value to the mobile build, and shows xcrun command invocations when enabled.

Leaves other flags as they are.

[andydotxyz]

I think this really brings the conversation over from the last issue as to what is the difference between verbose and debug?

I am trying to read up on what other places do and it seems (at a glance?) that verbose is about command output and debug is about replicating steps used to create that result (i.e. command logging).

See how the mobile package uses buildV to set the stdout and stderr to pass through, but does not (at least in iOS) pass the commands used to the output. It's buildX that is used to print things like the mkdir etc.

[sdassow]

I think this really brings the conversation over from the last issue as to what is the difference between verbose and debug?

I am trying to read up on what other places do and it seems (at a glance?) that verbose is about command output and debug is about replicating steps used to create that result (i.e. command logging).

From other tools I'm used to verbose showing commands etc, and passwords and stuff only with debug enabled. Some tools use multiple verbose flags for that, indicating that we're talking about log levels I think.

See how the mobile package uses buildV to set the stdout and stderr to pass through, but does not (at least in iOS) pass the commands used to the output. It's buildX that is used to print things like the mkdir etc.

Oh, if the wires are crossed like this (different flags for different tools), then I missed it and wasn't clear to me from the original PR discussion.

[andydotxyz]

I don't have the answers but did want to highlight the potential confusion here. What should verbose be outputting and what should it not - and is the other stuff outputted by a debug flag...