[Data Factory] Add readBehavior property to Salesforce Source in SDK

[smilenow]

Description

• Swagger spec has been merged: [Swagger Change] Add readBehavior property to Salesforce Source azure-rest-api-specs#2085
• This SDK change is internal reviewed at: http://codeflow/extensions/launcher.html?server=https:%2f%2fmsdata.visualstudio.com%2fdefaultcollection&projectId=13ee5071-298b-4fbc-863a-5ffe8c09e915&reviewId=85145&projectshortname=Azure Data Factory
• And it has been internal approved via https://msdata.visualstudio.com/Azure%20Data%20Factory/Azure%20Data%20Factory%20Team/_workitems/edit/109555

---

This checklist is used to make sure that common guidelines for a pull request are followed.

• Please add REST spec PR link to the SDK PR
• I have read the contribution guidelines.
• The pull request does not introduce breaking changes.

General Guidelines

• Title of the pull request 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 more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

• Pull request includes test coverage for the included changes.

SDK Generation Guidelines

• If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
• The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code.
• The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK.

[shahabhijeet]

use generate.cmd to generate your sdk. I need to see the generated metadata.txt file in this pr.

[shahabhijeet]

@smilenow why are you generating from your repo? This has to be generated from main azure fork and not yours?

[smilenow]

Because previously I heard from @gadongji , it could be OK no matter which branch is used to generated. But anyway, I will resolve the conflict and then re-generated by using the Azure fork branch.

[shahabhijeet]

@smilenow I don't see the commit Id for the spec that is part of the meta data file?
Are you generating from the merged spec?

[smilenow]

@shahabhijeet Yes, I was generating from the Azure latest public repo yesterday, and didn't modify anything in this file. Do you mean it should input a certain commit id when using generate.cmd?

[smilenow]

@shahabhijeet , shall we go ahead with this PR? Or do you need a exact commit id when generating the SDK from the swagger spec?

[shahabhijeet]

@smilenow please take a look at the file which no longer has the commit Id.
When you use generate.cmd, it actually not only generates the SDK, it goes and fetches the latest commit Id of your REST api spec and puts it into the .txt file.
In your latest change that commit id is not available.
Everytime you generated it basically tells that this particular generated code is from a particular commit Id of your spec.