Have nsc URL operator, account, user take precedence over environment

[bruth]

I observed the behavior of trying to generate a profile, e.g. nsc generate profile nsc://hub/APP/user while my nsc environment was set to a different operator. The command failed in the validation check.

Knowing there are several forms of the URL that can be specified, my expectation would be that if all components (operator, account, user) are specified in the URL, it would ignore whatever is set in nsc env. If any components are missing, then it would fallback to the env.