[Cosmos] disable api version check for new pylint requirements

[simorenoh]

From https://azure.github.io/azure-sdk/python_design.html#python-client-constructor-api-version-argument-1

These guidelines will now begin to be enforced starting 04/15, so making this PR pre-emptively to unblock Cosmos once this check goes out (since it will block our pylint check in the pipelines). Can't merge this until those changes are out but wanted to get ahead of it.

[azure-sdk]

API change check for azure-cosmos

API changes have been detected in azure-cosmos. You can review API changes here

API changes

-     cvar CurrentVersion = 2018-12-31
-     cvar QueryVersion = 1.0
-     cvar SDKName = azure-cosmos
+     cvar SDK_name = azure-cosmos
+     cvar api_versions = ['2018-06-18', '2018-08-31', '2018-09-17', '2018-12-31', '2019-10-14', '2020-07-15', '2020-11-05']
+     cvar current_version = 2018-12-31
+     cvar query_version = 1.0

[simorenoh]

/azp run python - cosmos - ci

[azure-pipelines]

Pull request contains merge conflicts.

[check-enforcer]

This pull request is protected by Check Enforcer.

What is Check Enforcer?

Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass.

Why am I getting this message?

You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged.

What should I do now?

If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows:
/check-enforcer evaluate
Typically evaulation only takes a few seconds. If you know that your pull request is not covered by a pipeline and this is expected you can override Check Enforcer using the following command:
/check-enforcer override
Note that using the override command triggers alerts so that follow-up investigations can occur (PRs still need to be approved as normal).

What if I am onboarding a new service?

Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment:
/azp run prepare-pipelines
This will run a pipeline that analyzes the source tree and creates the pipelines necessary to build and validate your pull request. Once the pipeline has been created you can trigger the pipeline using the following comment:
/azp run python - [service] - ci

[simorenoh]

/azp run python - cosmos - ci

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[kushagraThapar]

This concept does not applies to Cosmos DB at all. Our SDK has more functionality than just serving as a wrapper for the REST calls - we don't support older API versions in our later SDKs.

Also when we introduce direct mode for the SDK these changes would even become useless for instance as at that point there is no REST API call.

This is not something that we do in any of our other SDKs.. (Java, .Net, NodeJS, GO SDK)

[johanste]

Let's make sure we are not doing breaking changes to make the linter happy. If this is a change to something that hasn't already been released, then it is goodness...

changes made

[tjprescott]

Tracking issue for this topic here: #24094