ESLint: cleanup await expect from protractor tests

[DenysVuika]

Please check if the PR fulfills these requirements

• The commit message follows our guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (check one with "x")

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Documentation
• Other... Please describe:

What is the current behaviour? (You can also link to an open issue here)

the @typescript-eslint/await-thenable prevents modified e2e files to be checked in unless all the expect await errors are fixed

What is the new behaviour?

• cleanup old protractor tests to respect the @typescript-eslint/await-thenable eslint rule
• fix errors with double quotes in strings (e2e)
• fix code formatting in various old e2e files
• fix missing documentation tags in e2e utility functions

Does this PR introduce a breaking change? (check one with "x")

• Yes
• No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...

Other information:

[DaryaBalvanovich]

Great refactor 🙂

[sonarcloud]

Quality Gate failed

Failed conditions
11.7% Duplication on New Code (required ≤ 3%)

See analysis details on SonarCloud