feat: track migration modal close event in Matomo

[kgarbacinski]

Description

Definition of Done

1. If required, the desciption of your change is added to the QA changelog
2. Acceptance criteria are met.
3. PR is manually tested before the merge by developer(s).
   • Happy path is manually checked.
4. PR is manually tested by QA when their assistance is required (1).
   • Octant Areas & Test Cases are checked for impact and updated if required (2).
5. Unit tests are added unless there is a reason to omit them.
6. Automated tests are added when required.
7. The code is merged.
8. Tech documentation is added / updated, reviewed and approved (including mandatory approval by a code owner, should such exist for changed files).
   • BE: Swagger documentation is updated.
9. When required by QA:
   • Deployed to the relevant environment.
   • Passed system tests.

---

(1) Developer(s) in coordination with QA decide whether it's required. For small tickets introducing small changes QA assistance is most probably not required.

(2) Octant Areas & Test Cases.

[linear]

DAPP-1544 Extend matomo to track closing the modal

[aziolek]

Modal can be closed before or after making a migration. Do we truly want to track that this way? May be hard to identify the conversion rate.