* First status check request after 20 seconds may confuse users making
them think that something going wrong
* Fixed a reason of a big amount status check requests (repeated calls
for listen() method) when user go from Tasks -> any other page -> Tasks
-> any other page -> Task -> any other page -> Task, etc not closing the
tab.
* Fixed bug when the progress invisible if the app initialized on task
page
* Fixed 403 code when user tries to cancel automatic annotation
* Added missed schema endpoint
* Added more informative progress (for queued/in progress/fail):

<img width="756" alt="image"
src="https://github.com/opencv/cvat/assets/40690378/f01c45a8-a460-48c0-bec4-88266bb65a2c">
<img width="980" alt="image"
src="https://github.com/opencv/cvat/assets/40690378/f9e2c5ad-c2b7-4c43-8214-34236f38103b">

<!-- Raise an issue to propose your change
(https://github.com/opencv/cvat/issues).
It helps to avoid duplication of efforts from multiple independent
contributors.
Discuss your ideas with maintainers to be sure that changes will be
approved and merged.
Read the [Contribution
guide](https://opencv.github.io/cvat/docs/contributing/). -->

<!-- Provide a general summary of your changes in the Title above -->

### Motivation and context
<!-- Why is this change required? What problem does it solve? If it
fixes an open
issue, please link to the issue here. Describe your changes in detail,
add
screenshots. -->
There is no way to know it is in validation except going inside the task
itself. It can be tedious, just to check the status.
With this improvement summary of job stages is revealed on task itself.

### How has this been tested?
<!-- Please describe in detail how you tested your changes.
Include details of your testing environment, and the tests you ran to
see how your change affects other areas of the code, etc. -->
It was tested manually

### Checklist
<!-- Go over all the following points, and put an `x` in all the boxes
that apply.
If an item isn't applicable for some reason, then ~~explicitly
strikethrough~~ the whole
line. If you don't do that, GitHub will show incorrect progress for the
pull request.
If you're unsure about any of these, don't hesitate to ask. We're here
to help! -->
- [x] I submit my changes into the `develop` branch
- [ ] I have added a description of my changes into the
[CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md)
file
- [ ] I have updated the documentation accordingly
- [ ] I have added tests to cover my changes
- [ ] I have linked related issues (see [GitHub docs](

https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword))
- [ ] I have increased versions of npm packages if it is necessary

([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning),

[cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning),

[cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning)
and

[cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning))

Example:

![2023-02-17_11-36](https://user-images.githubusercontent.com/57707673/219599239-865458a9-daaf-4e72-85cc-6c1652086c4b.png)



### License

- [x] I submit _my code changes_ under the same [MIT License](
https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the
project.
  Feel free to contact the maintainers if that's a concern.

---------
Co-authored-by: NBoris Sekachev <boris@cvat.ai>

* Popover trigger on click, shared tooltip component

* Aborted trigger

* Updated version

* Added automatic annotation progress to the task view

* Updated changelog & version
Co-authored-by: NNikita Manovich <nikita.manovich@intel.com>