We should have a consistent way of ignoring parameters

[tjprescott]

We should have a consistent way to ignore parameters (particularly SDK parameters) so that they don't appear in tab completion and that an appropriate error is thrown if they are specified (which should be unrecognized argument).

Because this would require smart creates (one of the most common uses of ignored parameters) to be retested, I'm breaking this up into tasks.

• update resource module (PR [Resource] Resource Tag Fix (issue 763) #765)
• update VM/VMSS create
• update network NIC create
• update network application-gateway create
• update network public-ip create
• update network lb create
• update network vpn-connection create
• update network traffic manager create

[tjprescott]

PR #681 defines a CliArgumentType (IGNORE_TYPE) that standardizes the behavior with regards to argparse somewhat. If specified it will treat the parameter as unrecognized, ensuring the logic, not the user, determines the value. However, this does not address removing the hidden parameter from tab completion.

[tjprescott]

This is tied somewhat to #731 because this will potentially require re-recording many long running tests. Thus I'll move this back into the backlog.

[tjprescott]

I believe this is pretty much done, but I will verify in Sprint 18.