Fixing examples and adding missed properties

[ms-premp]

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.

PR information

• [Y] The title of the PR is clear and informative.
• [Y] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
• [Y] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
• If applicable, the PR references the bug/issue that it fixes.
• [Y] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

• [Y] I have read the contribution guidelines.
• [Y] My spec meets the review criteria:
  • [Y] The spec conforms to the Swagger 2.0 specification.
  • [Y] The spec follows the guidelines described in the Swagger checklist document.
  • [Y] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

[AutorestCI]

Automation for azure-sdk-for-js

Nothing to generate for azure-sdk-for-js

[AutorestCI]

Automation for azure-sdk-for-python

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-python#2924

[azuresdkci]

Can one of the admins verify this patch?

[AutorestCI]

Automation for azure-sdk-for-node

Nothing to generate for azure-sdk-for-node

[AutorestCI]

Automation for azure-sdk-for-java

Nothing to generate for azure-sdk-for-java

[AutorestCI]

Automation for azure-sdk-for-ruby

Nothing to generate for azure-sdk-for-ruby

[AutorestCI]

Automation for azure-sdk-for-go

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-go#2897

[hovsepm]

@ms-premp please take a look to validator errors as well:

Validating "examples" and "x-ms-examples" in  specification/cost-management/resource-manager/Microsoft.CostManagement/stable/2018-05-31/costmanagement.json:
 error : 
operationId: BillingAccountDimensions_List
scenario: BillingAccountDimensionsListExpandAndTop
source: request
responseCode: ALL
severity: 0
errorCode: INVALID_TYPE
errorDetails:
  code: INVALID_TYPE
  params:
    - integer
    - string
  message: Expected type integer but found type string
  path: >-
    /providers/Microsoft.Billing/billingAccounts/{billingAccountId}/providers/Microsoft.CostManagement/dimensions/$top
 error : 
operationId: BillingAccountDimensions_List
scenario: BillingAccountDimensionsListWithFilter
source: request
responseCode: ALL
severity: 0
errorCode: INVALID_TYPE
errorDetails:
  code: INVALID_TYPE
  params:
    - integer
    - string
  message: Expected type integer but found type string
  path: >-
    /providers/Microsoft.Billing/billingAccounts/{billingAccountId}/providers/Microsoft.CostManagement/dimensions/$top
 error : 
operationId: SubscriptionDimensions_List
scenario: SubscriptionDimensionsList
source: request
responseCode: ALL
severity: 0
errorCode: INVALID_TYPE
errorDetails:
  code: INVALID_TYPE
  params:
    - integer
    - string
  message: Expected type integer but found type string
  path: >-
    /subscriptions/{subscriptionId}/providers/Microsoft.CostManagement/dimensions/$top
 error : 
operationId: ResourceGroupDimensions_List
scenario: ResourceGroupDimensionsList
source: request
responseCode: ALL
severity: 0
errorCode: INVALID_TYPE
errorDetails:
  code: INVALID_TYPE
  params:
    - integer
    - string
  message: Expected type integer but found type string
  path: >-
    /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.CostManagement/dimensions/$top
Validating "examples" and "x-ms-examples" in  specification/cost-management/resource-manager/Microsoft.CostManagement/stable/2018-08-31/costmanagement.json: