Introduced annotations actions

[bsekachev]

Motivation and context

Actions are scripts, automatically modifying annotations within a job in certain ways
For example can be used to convert shapes from one type to another one. Potentially they may implement many different things

Related #954

But the issue is about tracks.
Added action allows removing for example:

• Small shapes
• Shapes with a specific label
• Shapes of a specific type, or with a specific attribute, etc

TODOs until PR is ready:

• consider rotation when converting rectangles
• finish checks in conversion worker
• handle close, handle cancel
• render parameters and pass them to action
• fix jest testing
• changelog, versions
• running on one object think how to implement

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.

[codecov]

Codecov Report

Merging #7172 (dc07c59) into develop (eba928c) will decrease coverage by 0.15%.
Report is 5 commits behind head on develop.
The diff coverage is 64.43%.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #7172      +/-   ##
===========================================
- Coverage    81.47%   81.33%   -0.15%     
===========================================
  Files          365      366       +1     
  Lines        39923    39357     -566     
  Branches      3703     3644      -59     
===========================================
- Hits         32528    32010     -518     
+ Misses        7395     7347      -48     

Components	Coverage Δ
cvat-ui	75.00% <64.43%> (-0.49%)	⬇️
cvat-server	87.09% <ø> (-0.01%)	⬇️

[klakhov]

I would propose:

• to hide Setup action parameters section if there are no parameters
• add more space between sections (margin-top: 56px, or a bit less)
  

[bsekachev]

to hide Setup action parameters section if there are no parameters

@klakhov

If get parameters() returns null, it is hidden:

You may already find this logic in the code:

How did you get it shown?

[bsekachev]

add more space between sections (margin-top: 56px, or a bit less)

Set 40px.

[klakhov]

Everything looks good for me now.

Just as small improvement, lets keep big margin in between sections, and a bit smaller one inside the section. Screenshot with 24px