Quality control page

[klakhov]

Motivation and context

Depends on #8323 - Removing quality control tab from analytics #8321 - New quality settings (Server) #8347 - New quality settings (UI)

How has this been tested?

Checklist

• [x] I submit my changes into the develop branch
• [x] 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)~~
• [x] I have increased versions of npm packages if it is necessary (cvat-canvas, cvat-core, cvat-data and cvat-ui)

License

• [x] 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 a dedicated Quality Control page for improved access to quality management tasks.
  • Added functionality to enable or disable ground truth (GT) frames on the Quality Control page.
  • Enhanced task creation with a Quality Configuration Form for setting validation methods and parameters.
  • Integrated a new action for Quality Control in the Actions Menu.
  • Added a Paid Feature Placeholder to highlight premium features.

• Bug Fixes

  • Improved error handling for frame deletion and restoration processes.

• Documentation

  • Updated configuration files to include details about the new Quality Control feature.

• Style

  • Updated styles for new components and adjusted layout for improved user experience.

• Refactor

  • Streamlined job management functions to focus on delete, export, and import actions.