Audio upload handler

[kushalpoddar]

Motivation and context

How has this been tested?

Checklist

• I submit my changes into the develop branch
• I have created a changelog fragment
• I have updated the documentation accordingly
• I have added tests to cover my changes
• I have linked related issues (see 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.

Summary by CodeRabbit

• New Features

  • Introduced functionality for exporting and importing datasets in YOLO format as ZIP files.
  • Enhanced audio data export capabilities including support for various audio-related attributes and formats.
  • Added new audio annotation features in the application models and database schema.
  • Updated email settings to disable mandatory email verification.

• Bug Fixes

  • Corrected a file path typo in source path configuration.

• Documentation

  • Updated environment variables in .vscode/launch.json by removing specific DJANGO log server settings.

• Refactor

  • Modified various functions to support new audio processing and export features.

• Chores

  • Added new dependencies to support audio processing (soundfile and pydub).

• Tests

  • No specific changes mentioned for tests.

• Style

  • No specific changes mentioned for style adjustments.

• Revert

  • No specific changes mentioned for reverts.

[nmanovic]

@kushalpoddar , thank you for the PR! Could you please add CHANGELOG? Could you please add instructions and some information about how to use the server with Audino UI?

[kushalpoddar]

Hi @nmanovic please checkout this branch and readme for the frontend. For no we have just allowed a wav audio file to be uploaded and played. It the code seems fine, we can build more over it with your help. As requested this is a basic prototype

https://github.com/midas-research/audino-frontend/tree/feat/cvat

[nmanovic]

Just for your information: https://github.com/adamchainz/django-cors-headers/blob/6f3fe99724bf42e57b062c8959792ca94c669ab0/README.rst#cors_allow_all_origins-bool

Setting this to True can be dangerous, as it allows any website to make cross-origin requests to yours. Generally you'll want to restrict the list of allowed origins with CORS_ALLOWED_ORIGINS or CORS_ALLOWED_ORIGIN_REGEXES.

It is a bad security practice. CVAT repo doesn't need the change, you don't need as well. It is better to list some specific origins. For the development purpose, it is better to run your own CVAT instance and specify additional settings.

@azhavoro , FYI.

[KTXKIKI]

so What progress has been made?

[sonarqubecloud]

Quality Gate failed

Failed conditions
8 Security Hotspots
30.3% Duplication on New Code (required ≤ 3%)
C Reliability Rating on New Code (required ≥ A)

See analysis details on SonarCloud

Catch issues before they fail your Quality Gate with our IDE extension SonarLint

[bsekachev]

Hello,
As nobody contributes this pull request, I will close it.

[nmanovic]

@midas-ai , feel free to reopen after you sync changes