Markdown documentation for tasks/projects

[bsekachev]

Motivation and context

Resolved #287
Resolved #3680
Resolved #5580

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)

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.

[klakhov]

When I'm trying to open markdown setup guide page, an error occurs:

I can't create guide for the same reason. Am I doing something wrong?
Request payload seems ok. Task definitely exists.

CVAT is deployed in clean dev environment

[bsekachev]

When I'm trying to open markdown setup guide page, an error occurs:

@klakhov
Do you use the latest version? There was such error, but I fixed it

[klakhov]

When I'm trying to open markdown setup guide page, an error occurs:

@klakhov Do you use the latest version? There was such error, but I fixed it

Yes, updating branch helped to fix that

[klakhov]

Should edit button be on the right? Maybe use

icon instead. It would look with issue tracker.
And Task description on project page seems a bit strange. Maybe its better to be named Description for tasks or Tasks description

[bsekachev]

Should edit button be on the right? Maybe use

This is the latest design from Breeze

Task description on project page seems a bit strange

I will fix it