Running detectors on the fly

[bsekachev]

Motivation and context

Our customers asked as to implement the feature that allows to annotate only one specific frame with automatic detectors
Resolve #197
The PR depends on #2054

How has this been tested?

Manual testing

Checklist

• I submit my changes into the develop branch
• I have added description of my changes into CHANGELOG file
• I have updated the documentation accordingly
• I have added tests to cover my changes
• I have linked related issues (read 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.
• I have updated the license header for each file (see an example below)

# Copyright (C) 2020 Intel Corporation
#
# SPDX-License-Identifier: MIT

• Show only detectors on annotation view
• Add ability to cancel annotation request
• Prettify UI

[coveralls]

Pull Request Test Coverage Report for Build 7283

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 70.67%

---

Totals
Change from base Build 7280:	0.0%
Covered Lines:	12409
Relevant Lines:	17164

---

💛 - Coveralls

[nmanovic]

Please don't assume that if we map all labels from the task, it is enough. In general I can want to map multiple labels to one. For example, { car -> vehicle, bus -> vehicle, truck -> vehicle }.

Can we adjust labels by columns? The new version:

The dialog below looks much better in the old version:

[bsekachev]

@nmanovic Sure. I will fix it.

[bsekachev]

@nmanovic

Fixed comments.
Also looks like found the issue why server returns all detections (with labels that absent in mapping). The client didn't sent mapping to the server.

[nmanovic]

Colors for labels should be taken from the task itself. Now "person" each time has own random color.