[ACR] Add ACR Build commands

[djyou]

---

This checklist is used to make sure that common guidelines for a pull request are followed.

• The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

• I adhere to the Command Guidelines.

[promptws]

View a preview at https://prompt.ws/r/Azure/azure-cli/6241
This is an experimental preview for @microsoft users.

[derekbekoe]

The PR contains privates/azure_mgmt_containerregistry-2.0.0-py2.py3-none-any.whl.
This SDK should be published before this is merged.

[djyou]

@derekbekoe Yes we wanted to start the review process while working on publishing the new SDK Azure/azure-sdk-for-python#1935. I also owe tests for the new commands and will add them shortly.

[derekbekoe]

What's $PAT?
Would suggest a different example value here?

[derekbekoe]

Same here with $PAT

[derekbekoe]

A FileCompleter may be useful here?

[derekbekoe]

Much prefer using SDK values when possible.
Why this change? Does the SDK no longer document the skus available?

[derekbekoe]

Use logger.warning for these user style messages.

[derekbekoe]

Same with below on messages like 'Waiting for a build agent...' etc.

By using logger, the messages go to stderr instead of stdout.

[derekbekoe]

You may want to suppress your current extension as well?
See https://github.com/Azure/azure-cli/blob/e7ca2aefa479829496fa35f17ce7dc36880e473a/doc/authoring_command_modules/authoring_commands.md#extension-suppression

An example here - https://github.com/Azure/azure-cli/blob/dev/src/command_modules/azure-cli-rdbms/azure/cli/command_modules/rdbms/__init__.py#L24-L29

[djyou]

@derekbekoe CI seems to be complaining the use of positional parameters. Could you please advise? We only have one such parameter.

[djyou]

/cc @sajayantony @ankurkhemani @northtyphoon @ehotinger @NatalieGong

[djyou]

/cc @mmacy @SteveLas for doc review and suggestions.

[tjprescott]

Also, please show the -h output for the new commands.

[tjprescott]

You should not use this.

[tjprescott]

Why a debug message and potentially unexpected behavior rather than a CLIError?

[djyou]

We have a few cases that the response doesn't have the datetime yet. For example, if users trigger a build and immediately get the status of it before it finishes, we don't have a finish time here. This is table formatting path and we thought we can just show empty in the column rather than throwing an error.

[tjprescott]

Same here--if the user inputs an invalid format, then failing silently and having unexpected behavior is probably not better than throwing an error.

[djyou]

This is the same reason as above handling response datetime. We don't format user inputs here. In this case, finish_time could be empty.

[tjprescott]

I didn't notice this was for table format. Displaying blank is completely appropriate.

[tjprescott]

For anywhere and everywhere "BOOL_CHOICES" is used, see:
https://github.com/Azure/azure-cli/blob/dev/doc/authoring_command_modules/authoring_commands.md#registering-flags

[tjprescott]

@djyou reviewing the stack trace, it looks like certain stages of the CI load parameters twice, which is why your one positional argument is being found twice and throwing an error. I'll make a PR to fix this.

[tjprescott]

@derekbekoe I recommend we merge this. No idea what's going on with CI and it's recent constant timeouts on Integration.