Hongtu/change fabricbot.json

[greathongtu]

Description

• Use powershell to sort taskType: scheduledAndTrigger part of fabricbot.json according to the table of Service-Team-Label-and-Contact-List.
  • It is sorted by labels name in ascending order.
  • So that we can create a pipeline in internal project to update this fabricbot.json automaticly further.
  • Add 27 new labels: Confidential Ledger, Consumption, Consumption- RIandShowBack ,Consumption-Billing, Consumption-Budget, Consumption-Consumption, Consumption-Query, Consumption-UsageDetailsandExport, Container App, Cost Management, Cost Management-Billing, Cost Management-Budget, Cost Management-Query, Cost Management-RIandShowBack, Cost Management-UsageDetailsAndExport, DataProtection, IotCentral, IotDPS, IotHub, MySQL - Flexible, Network - ExpressRoutes, PostgreSQL - Flexible, PowerBI, Quantum, Serial Console, Spring Cloud, WebPubSub
  • Remove 11 labels that don't exist in wiki page: Network - ExpressRoute, Cost Management - Budget, Cost Management - Query, Consumption - Query, Cost Management - Billing, Consumption - Billing, Cost Management - UsageDetailsAndExport, Consumption - UsageDetailsAndExport, Cost Management - RIandShowBack, Consumption - RIandShowBack, Consumption - Budget

Checklist

• Check this box to confirm: I have read the Submitting Changes section of CONTRIBUTING.md and reviewed the following information:

• SHOULD select appropriate branch. Cmdlets from Autorest.PowerShell should go to generation branch.
• SHOULD make the title of PR clear and informative, and in the present imperative tense.
• SHOULD update ChangeLog.md file(s) appropriately
  • For any service, the ChangeLog.md file can be found at src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
  • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header in the past tense. Add changelog in description section if PR goes into generation branch.
  • Should not change ChangeLog.md if no new release is required, such as fixing test case only.
• SHOULD have approved design review for the changes in this repository (Microsoft internal only) with following situations
  • Create new module from scratch
  • Create new resource types which are not easy to conform to Azure PowerShell Design Guidelines
  • Create new resource type which name doesn't use module name as prefix
  • Have design question before implementation
• SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
• SHOULD have proper test coverage for changes in pull request.
• SHOULD NOT introduce breaking changes in Az minor release except preview version.
• SHOULD NOT adjust version of module manually in pull request

[dingmeng-xue]

/azp run azure-powershell - security-tools

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).