feat: integration tests setup

[pcheremu]

What ❔

no changes with integration-tests branch except fixed commit signatures

Integration tests setup

Why ❔

Checklist

• [ ] PR title corresponds to the body of PR (we generate changelog entries from PRs).
• [ ] Tests for the changes have been added / updated.
• [ ] Documentation comments have been added / updated.

[github-actions[bot]]

Unit Test Results

    4 files    261 suites   11m 14s :stopwatch: 2 075 tests 2 074 :white_check_mark: 1 :zzz: 0 :x: 2 272 runs  2 271 :white_check_mark: 1 :zzz: 0 :x:

Results for commit 3dd0c6c4.

:recycle: This comment has been updated with latest results.

[github-actions[bot]]

API E2E Test Results

207 tests   207 :white_check_mark:  19s :stopwatch:  14 suites    0 :zzz:   1 files      0 :x:

Results for commit 3dd0c6c4.

:recycle: This comment has been updated with latest results.

[github-actions[bot]]

Visit the preview URL for this PR (updated for commit 85e5adc):

• https://staging-scan-v2--pr177-integration-tests-si-f3ultg6s.web.app
• https://staging-storybook-scan-v2--pr177-integration-tests-si-aa7ooap4.web.app

_{(expires Wed, 05 Jun 2024 15:33:59 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

_{Sign: e508f9012944951194447cb8885950b451a24403}

[pcheremu]

@Romsters @vasyl-ivanchuk @abilevych After the warning "branch is out-of-date", it requires the rebase from the very beginning, with a lot of attention. This PR is too complicated and too heavy to do it regularly. Should I create a simple PR with 1 commit that will be based on the main branch that will contains only changes that belongs to integration-tests?

[github-actions[bot]]

Visit the preview URL for this PR: https://staging-scan-v2--pr-177-beezn3k1.web.app