Consensus simple merging

[zhiltsov-max]

Motivation and context

Depends on #8939, #9026
A part of #8434

• Added support for consensus task and consensus job merging (API and UI)
• Added simple consensus settings
• Added server tests
• Added new consensus RQ queue and worker

Limitations:

• Merging is supported for all annotations except 2d and 3d cuboids. 3d tasks are not supported
• Annotation groups are not supported (each annotation is considered separate in a group)
• Polygons and masks are not interchangeable (each type is compared only with the same type)

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.

[SpecLad]

Do we really need another worker for this? Can't an existing worker, like the quality report worker, handle this?

[zhiltsov-max]

Currently, we add a worker almost for any new activity, so this PR does the same. Probably, it can be optimized.

[SpecLad]

We should be using the request API for status checking.

[zhiltsov-max]

Currently, the reason is that Requests API v2 is not implemented yet. It's hard to integrate anything except import or export into the same server code. Supporting other use cases is one of the key goals of v2.

[sonarqubecloud]

Quality Gate failed

Failed conditions
C Security Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

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