Add layer 2 of SDK

[zhiltsov-max]

Motivation and context

• Added launch.json tasks for python tests
• Server:
  • Fixed response schema for MetaUser and PolymorphicProject (oneOf -> anyOf)
• SDK:
  • Fixed cloudstorage api operation names (removed api prefix, removed the dash in the middle of api)
  • Fixed Ignore files
  • Added cookie management in ApiClient
  • Added hostname fixing in Configuration (trailing slashes are removed automatically)
  • Added automatic schema detection in ApiClient
  • Fixed method docstrings to be displayed correctly in VS Code (added a separating line)
  • Fixed Configuration class docstrings
  • Added json serialization function for models
  • Added layer 2 of SDK, which contains various usecases, utilities and composite operations
    • Currently, only covers task operations (the same as CLI.core module did)
  • Updated sdk library file layout
  • Added generated files to .gitignore, except documentation (need to start publishing it in the future)
• CLI:
  • Implementation is completely rewritten to use SDK
    • Removed CLI.core module
  • Aadded with_images option to download annotations and images in dump
  • Added options to control status check periods in export and import
  • Tests moved to tests/ next to rest-api/
• Upgraded pylint version to 2.14 and migrated .pylintrc
• Enabled pylint, black and isort for tests, cvat-cli and cvat-sdk modules on CI. Keep in mind that different modules need to be processed by different runs of black/isort, otherwise we get invalid behaviour.

How has this been tested?

Unit tests

Checklist

• [ ] I submit my changes into the develop branch
• [ ] I have added a description of my changes into CHANGELOG file
• [ ] I have updated the documentation accordingly
• [ ] I have added tests to cover my changes
• [ ] I have linked related issues (read github docs)
• [ ] I have increased versions of npm packages if it is necessary (cvat-canvas, cvat-core, cvat-data and cvat-ui)

License

• [ ] I submit my code changes under the same MIT License that covers the project. Feel free to contact the maintainers if that's a concern.

[nmanovic]

Hi @JulianWgs ,

Thank you for the bug report. Checking input is an important task and we will try to improve it into our next major release.