Removed analytics reports

[bsekachev]

Motivation and context

Current implementation is not efficient enough and barely used.
This feature is going to be re-implemented in another way.

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 78.57143% with 3 lines in your changes missing coverage. Please review.

Project coverage is 73.81%. Comparing base (fa4934d) to head (3fbc0f8).
Report is 2 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #9174      +/-   ##
===========================================
+ Coverage    73.32%   73.81%   +0.48%     
===========================================
  Files          449      427      -22     
  Lines        45875    44969     -906     
  Branches      3915     3915              
===========================================
- Hits         33640    33193     -447     
+ Misses       12235    11776     -459     

Components	Coverage Δ
cvat-ui	76.61% <78.57%> (-0.49%)	⬇️
cvat-server	71.48% <84.90%> (+1.17%)	⬆️

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

[sonarqubecloud]

Quality Gate passed

Issues
7 New issues
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