Honey pot UI

[zhiltsov-max]

Motivation and context

Depends on #6204

• Added UI for the Honey Pot feature

How has this been tested?

Checklist

• I submit my changes into the develop branch
• I have added a description of my changes into the CHANGELOG file
• 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)

Information about comments

• Fixed aligns of preview and assignee on task page
• Added margin in the end of job list on task page
• Solved/Unsolved issues for Job are kept on place, we can think about removing them in PR with analytics page
  
• Copy Job list button was restored to it's place
• Added borders and border highlight like on task card for job card
• Changed "0%" to "<1%"
  
• Submit and Submit and Open button. I think we should keep those buttons for consistency. In any case user can decide by himself what he wants, just create and go back or immediately go to GT job
• About GT job issues and participating in computing completion progress
  These jobs still have to be annotated and reviewed by someone in the annotation team, it makes sense to treat their progress equally with other jobs.
• Space in submit form.
  Personally, I think without it, form looks too short and page becomes empty.
• Frame intercesction (as all data on Quality page) is extracted from Quality report, so currently we wont show it immidiately
• Tracks are now shown only on frames included in GT job
• Object menu in object sidebar is removed for GT annotation
• Sorting for conflcits/quality is fixed
• Frame intersection N/A and no ability to download the report means the report doesn't exist yet. We need to wait for it to be computed
• With fixed problem with tracks, there won't be any annotations on jobs with 0% intersection
• 2d cuboids and tags wont supported in this version
• Automatically go to the next frame in tag annotation mode
• Find empty frame navigation in GT job
• Delete frame in GT job
  Currently deleted frames are marked for a task, so deleting frame in GT deletes it everywhere. It really doesn't make sence to support deleting frames in GT jobs, So lets disable that option for now
• [ ] Broken top margin in the frame filter configuration dialog in the annotation page

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.

[bsekachev]

@klakhov

Submit and Submit and Open button. I think we should keep those buttons for consistency. In any case user can decide by himself what he wants, just create and go back or immediately go to GT job

There is no reason to stay on "Create GT job" page after GT job is already created because several GT jobs can not be created.
Two options I see: open GT job immediately, return to analytics page.

[klakhov]

@bsekachev

There is no reason to stay on "Create GT job" page after GT job is already created because several GT jobs can not be created. Two options I see: open GT job immediately, return to analytics page.

Ok, I see. Let's stick to the first option

[bsekachev]

Okay, let's solve conflicts wait for Andrey review and I believe we can merge it

[zhiltsov-max]

• It seems the report computation time info is missing (it was under the downloading button)
  

• Job actions menu needs to be fixed: the 3 to "Go To ..." buttons have no use outside the annotation window, probably need to add the black border around the menu
  

• Job frame filter has invalid top margin (it's a regression against develop)
  

[klakhov]

[x] It seems the report computation time info is missing (it was under the downloading button)

Fixed

[ ] Job actions menu needs to be fixed: the 3 to "Go To ..." buttons have no use outside the annotation window, probably need to add the black border around the menu

This menu is mutual for Jobs cards(on task and jobs pages), those buttons are used on Jobs Page mostly. I dont think we need 2 different menus

[x] Job frame filter has invalid top margin (it's a regression against develop)

Fixed

[zhiltsov-max]

This menu is mutual for Jobs cards(on task and jobs pages), those buttons are used on Jobs Page mostly. I dont think we need 2 different menus

Ok, but job menus on the task page have the same problem - the "Go To" buttons are not needed there.

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 24.16201% with 543 lines in your changes missing coverage. Please review.

Project coverage is 80.12%. Comparing base (ea6c68f) to head (4775e3f).
Report is 1451 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #6039      +/-   ##
===========================================
- Coverage    81.17%   80.12%   -1.05%     
===========================================
  Files          322      331       +9     
  Lines        37782    38431     +649     
  Branches      6821     6923     +102     
===========================================
+ Hits         30670    30794     +124     
- Misses        6803     7328     +525     
  Partials       309      309              

Components	Coverage Δ
cvat-ui	74.68% <24.16%> (-2.03%)	⬇️
cvat-server	85.17% <ø> (ø)

---- 🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests
• JS Bundle Analysis - Avoid shipping oversized bundles