Add profiles generation tool and init version of profiles

[tadelesh]

Partially resolve https://github.com/Azure/azure-sdk-for-go/issues/16830.

• Add some packages to generate mgmt. plane config and SDK for profile.
• First version of profile config 2020-09-01-hybrid package which only contains mgmt. plane modules.

[tadelesh]

/azp run prepare-pipelines

[azure-pipelines[bot]]

Azure Pipelines successfully started running 1 pipeline(s).

[jhendrixMSFT]

Few questions.

• Does this include full generated code, i.e. no removal of resource types?
• When will data-plane parts (i.e. key vault) be added?

[tadelesh]

Few questions.

• Does this include full generated code, i.e. no removal of resource types?
• When will data-plane parts (i.e. key vault) be added?

• Does this include full generated code, i.e. no removal of resource types? Yes. I found it's hard to pair the config with operation/operation group. For example, which operation belong to storageAccounts/blobServices in the spec according to this config. If I could figure out how to pair them, I think I could find some way to remove useless resource types.

• When will data-plane parts (i.e. key vault) be added? Since we will announce the deprecation for track1 publicly later this September, I think we need to finish the work before that. According to the issue, it seems we don't have a conclusion for how we add the data plane modules. Is there any update for this?

[tadelesh]

I've moved tooling change out of this PR and currently this PR should be a clear beta version for profile hybrid20200901, but only support mgmt. plane.

[jhendrixMSFT]

I see that the root build.go file was removed. While you don't have to fix it now, we really should ensure that all modules can be built via go generate.

[tadelesh]

I see that the root build.go file was removed. While you don't have to fix it now, we really should ensure that all modules can be built via go generate.

OK. I think if we decide to use profile, I'll do the fix.