[Cognitive Services] Mark id/kind/type fields as readOnly

[felixwa]

Mark id/kind/type fields as readOnly to make "AutoRest --azure-validator
--openapi-type=arm" happy.

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

• The title of the PR is clear and informative.
• 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.
• 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.
• Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

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

[azuresdkciprbot]

Hi There,

I am the AutoRest Linter Azure bot. I am here to help. My task is to analyze the situation from the AutoRest linter perspective. Please review the below analysis result:

File: specification/cognitiveservices/resource-manager/readme.md
Before the PR: Warning(s): 4 Error(s): 1
After the PR: Warning(s): 4 Error(s): 0

AutoRest Linter Guidelines | AutoRest Linter Issues

Send feedback and make AutoRest Linter Azure Bot smarter day by day!

Thanks for your co-operation.

[felixwa]

This PR fixes an Error (can be seen from Linter Azure bot):

Before the PR: Warning(s): 4 Error(s): 1
After the PR: Warning(s): 4 Error(s): 0

[balajikris]

Notice that this will be a breaking change for the SDKs, if you had shipped the existing schema as SDK packages. Make sure to version the newly generated packages appropriately to reflect the breaking change.

[balajikris]

while at it, can you also fix this failure in examples validation? : https://travis-ci.org/Azure/azure-rest-api-specs/jobs/268246587

[felixwa]

@balajikris , the validate-example issue (the type can be null) has been there for a while and last time @veronicagg mentioned that is because the issue of the validation tool. See: #798
Since the issue is still open I don't think I can fix it now.

[AutorestCI]

No modification for AutorestCI/azure-sdk-for-node

[AutorestCI]

Azure/azure-sdk-for-python#1397

[AutorestCI]

Azure/azure-sdk-for-ruby#928