Fix reset of attributes when moving a task to a project

[yasakova-anastasia]

Motivation and context

• Fixed reset of attributes when moving a task to a project

Steps to reproduce the bug:

1. Create a task with a couple of labels and attributes
2. Annotate several frames in the task. Attributes should have non-default value.
3. Create a project and copy the definition of labels with attributes
4. Move the task to the project.
5. Attributes should have default values after the action

How has this been tested?

Added REST API test

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)

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.

[sizov-kirill]

I see some strange behavior: try to create task with the following label configuration:

task configuration

``` [ { "name": "car", "id": 9, "color": "#2080c0", "type": "any", "attributes": [ { "id": 5, "name": "mark", "input_type": "select", "mutable": false, "values": [ "bmw", "audi", "fiat" ], "default_value": "bmw" } ] } ] ```

Annotate some frames and set some non-default attributes, then create project with the following label configuration

project configuration

[ { "name": "car", "id": 10, "color": "#2080c0", "type": "any", "attributes": [ { "id": 6, "name": "mark", "input_type": "select", "mutable": false, "values": [ "ford", "honda", "volvo" ], "default_value": "ford" } ] } ] ```

Then move annotated task into the project.

It's questionable should we allow to move task in project if project has the same label with the same name attributes but with different attributes spec

[yasakova-anastasia]

It's questionable should we allow to move task in project if project has the same label with the same name attributes but with different attributes spec

I think that the task with such attributes should not be moved. Expanded the check for this.

[sizov-kirill]

LGTM