CosmosDB Cassandra, Mongo, Table, Gremlin API with Management sdk 1.0.1

[MehaKaushik]

Description

Checklist

• I have read the Submitting Changes section of CONTRIBUTING.md
• The title of the PR is clear and informative
• The appropriate ChangeLog.md file(s) has been updated:
  • 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 -- no new version header should be added
• The PR does not introduce breaking changes
• If applicable, the changes made in the PR have proper test coverage
• For public API changes to cmdlets:
  • a cmdlet design review was approved for the changes in this repository (Microsoft internal only)
  • the markdown help files have been regenerated using the commands listed here

[MehaKaushik]

Hey, @VeryEarly are you reviewing this PR ??

[VeryEarly]

Changelog.md need to be updated.

Please also resolve conflicts in Az.CosmosDB.psd1

[MehaKaushik]

@VeryEarly
-> Reverted the breaking changes to include them in a subsequent PR.
-> Updated ChangeLog.md
-> Resolved Conflicts

[VeryEarly]

Hi @MehaKaushik ,

output type of New-AzCosmosDBSqlConflictResolutionPolicy was changed from "PSSqlConflictResolutionPolicy" to "PSConflictResolutionPolicy" which could be a breaking change. Can you add "PSSqlConflictResolutionPolicy.cs" back?

The help file New-AzCosmosDBSqlConflictResolutionPolicy.md should be also added back.

[MehaKaushik]

@VeryEarly Changed as suggested for New-AzCosmosDBSqlConflictResolutionPolicy as well as for New-AzCosmosDBSqlUniqueKey, New-AzCosmosDBSqlUniqueKeyPolicy and New-AzCosmosDBSqlndexingPolicy.

[MehaKaushik]

@VeryEarly What needs to be done to make this PR into the next release ??