Add asctime to uvicorn stdout logs

[Marishka17]

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)

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.

[Marishka17]

I'm not sure whether it is better to keep the logging config in django settings (one place with all configs) or provide a log config file by passing the --log-config option when running uvicorn.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 74.14%. Comparing base (17bb612) to head (03456e2).
Report is 1 commits behind head on develop.

Additional details and impacted files

@@           Coverage Diff            @@
##           develop    #9210   +/-   ##
========================================
  Coverage    74.14%   74.14%           
========================================
  Files          428      428           
  Lines        44973    44973           
  Branches      3917     3917           
========================================
  Hits         33345    33345           
  Misses       11628    11628           

Components	Coverage Δ
cvat-ui	77.22% <ø> (ø)
cvat-server	71.58% <ø> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[SpecLad]

Could you explain why you want to do this? Supervisor already adds the time.

[Marishka17]

Could you explain why you want to do this? Supervisor already adds the time.

just go to a container and check uvicorn logs in /tmp dir
@SpecLad, does this answer your question?

[SpecLad]

Could you add a changelog entry?

[sonarqubecloud]

Please retry analysis of this Pull-Request directly on SonarQube Cloud