Added simple test for analytics availability

[azhavoro]

Motivation and context

How has this been tested?

Checklist

• I submit my changes into the develop branch
  - [ ] I have added a description of my changes into CHANGELOG file
  - [ ] I have updated the documentation accordingly
  - [ ] I have added tests to cover my changes
  - [ ] I have linked related issues (read 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.
• I have updated the license header for each file (see an example below)

# Copyright (C) 2022 Intel Corporation
#
# SPDX-License-Identifier: MIT

[sizov-kirill]

Tests looks good to me, but I have one question. Did you try to see analytics on test DB?

When I tried to do it, analytics dashboards were empty and Kibana raises errors: Unable to update UI setting Request failed with status code: 406 and Error in visualization aggs is undefined, even though the test database has users and tasks, is this expected behavior for this database?

[azhavoro]

Tests looks good to me, but I have one question. Did you try to see analytics on test DB?

When I tried to do it, analytics dashboards were empty and Kibana raises errors: Unable to update UI setting Request failed with status code: 406 and Error in visualization aggs is undefined, even though the test database has users and tasks, is this expected behavior for this database?

This error appeared after #4239 PR was merged because it changes accept header for all CVAT endpoints, should be fixed now.

[sizov-kirill]

@azhavoro I slightly modified the test function so that it doesn't depend on usernames.

About viewing analytics with test db: I tested manually, now all works fine.

Are the changes in this PR related to the failure of UI tests?

[nmanovic]

LGTM