Streaming export for YOLO and COCO formats

[Eldies]

Motivation and context

Depends on cvat-ai/datumaro#81, cvat-ai/datumaro#90, cvat-ai/datumaro#94, #9209

When we export a dataset, all annotations are kept in RAM. It may be a problem if they are large.

• Added support for dataset streaming export for task or jobs
• Switched to streaming in COCO and YOLO export formats

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.

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 97.36842% with 1 line in your changes missing coverage. Please review.

Project coverage is 73.40%. Comparing base (39bcc6a) to head (6779f37).

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #9084      +/-   ##
===========================================
+ Coverage    73.38%   73.40%   +0.02%     
===========================================
  Files          450      450              
  Lines        45847    45866      +19     
  Branches      3917     3917              
===========================================
+ Hits         33645    33670      +25     
+ Misses       12202    12196       -6     

Components	Coverage Δ
cvat-ui	77.12% <ø> (+0.03%)	⬆️
cvat-server	70.43% <97.36%> (+0.01%)	⬆️

🚀 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.

[zhiltsov-max]

I've noticed export performance degradation in streaming mode for COCO formats, about 2-3x in my cases. As I understand it, the problem is in coco/exporter.py:142, where the regular json library is used instead of the optimized orjson. I suppose orjson isn't compatible directly with json stream used in the implementation now, but I could find that there is other relevant functionality in orjson - https://github.com/ijl/orjson?tab=readme-ov-file#fragment. Please check this issue.

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud