Use 'flowcrypt.com/shared-tenant-fes' instead of 'flowcrypt.com/api'

[DenBond7]

This PR added using 'flowcrypt.com/shared-tenant-fes' instead of 'flowcrypt.com/api'

close#2162
close#2138

---

Tests(delete all except exactly one):

• Tests added or updated

---

todo

• fix wrong behavior as in this comment (second point) test shared-tetant-fes for android app #2197 (comment)

---

To be filled by reviewers

I have reviewed that this PR... (tick whichever items you personally focused on during this review):

• addresses the issue it closes (if any)
• code is readable and understandable
• is accompanied with tests, or tests are not needed
• is free of vulnerabilities

[DenBond7]

@tomholub Please relook the current changes while I'm working on fixing tests.

[DenBond7]

@tomholub Please relook. I've added the requested changes.

[tomholub]

It's improving a lot, see comments

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	Secret	Commit	Filename
5943992	Generic High Entropy Secret	d3c4d75	FlowCrypt/src/enterpriseUiTests/res/values/api_keys.xml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

<sup>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sup>

[DenBond7]

@tomholub I think I've added changes that were requested to migrate to shared-tenant-fes. But all of these changes are related to the setup screen. we still don't support the following:

going forward, client continues attempting to call fes.domain.com first before falling back on flowcrypt.com/shared-tenant-fes anytime it needs to update Client Configuration, and continues using flowcrypt.com/shared-tenant-fes for password protected messages and all other APIs, for as long as fes.domain.com is not available.
if Client Configuration is ever successfully retrieved from fes.domain.com, the app will start using fes.domain.com for all APIs going forward.

it means we decide at the setup screen whether will we use a custom FES server or not. After the setup screen, we don't use a custom FES server if it failed at the setup screen.

If it is possible I propose adding that functionality via a separate PR. The current PR is already not simple.

If yes, I will ask Mart to recheck #2197 and after that, we will be ready to merge it.

[tomholub]

yes, the parts after setup can be done in a future version. so ok for @martgil to re check functionality now

[DenBond7]

@ioanmo226 Please make the final review.

[DenBond7]

Can I merge this PR with after my review? or waiting some other things?

Yes, we are ready to merge it.