chore: single locator constants file to be used for UI and main tests

[findms]

WPB-20289 [iOS/QA] Store all locators to a common file with common target to be available and used in Main+ UI tests

Issue

Issue to have separate locators for UI and main tests and some repetive locators against every page like OK, Done etc.

Changes

All the locators from page class now moved to a foundation file Locators.swift by which the same element can be used for both UI and main tests.

Testing

Ran all UI tests locally and worked fine

Optional: attachments like images, videos, etc.

---

Checklist

• Title contains a reference JIRA issue number like [WPB-XXX].
• Description is filled and free of optional paragraphs.
• Adds/updates automated tests.

---

UI accessibility checklist

If your PR includes UI changes, please utilize this checklist:

• Make sure you use the API for UI elements that support large fonts.
• All colors are taken from WireDesign.ColorTheme or constructed using WireDesign.BaseColorPalette.
• New UI elements have Accessibility strings for VoiceOver.

[github-actions]

Test Results

1 907 tests   1 880 ✅  2m 24s ⏱️
  307 suites     27 💤
    2 files        0 ❌

Results for commit 24a49c8.

[netbe]

The idea was to use the constants within the app, here the first part is done with using in the UITests. I expect the code within the app to be updated to merge this PR

[netbe]

thought: I wonder if that makes sense this organisation per type rather than per domain / page

[findms]

I think it makes more sense by type as there are some bottom sheet pages which has 1 or 2 usable elements + will be avoided duplicate elements like next confirm OK etc across various pages.

[findms]

New PR created #3653 as approach changed.