Add a staging configuration that automatically targets the staging environment

[buggmagnet]

This PR creates a staging environment. The API endpoint and IP are now hardcoded in the Api.xcconfig file.
The API endpoint and IP address are now loaded and stored in the Info.plist files of both the packet tunnel and the main host application.

In order to use the staging environment, In Xcode go to the following menu :
Product > Scheme > Edit Scheme
In the Run section, select the Staging environment

⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️

If you want to test this PR

• Copy the Api.xcconfig.template file and replace the values with the API endpoint, and the staging endpoint.
• Delete the application from your device
• Select the Staging build scheme
• Install the application

⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️

---

This change is 

[linear]

IOS-422 Add new build scheme to make dev and release builds that use the staging environment

[buggmagnet]

Looks like I forgot about GH CI, will fix soon

[pinkisemils]

Reviewed 2 of 10 files at r1, 2 of 10 files at r2.
Reviewable status: 4 of 16 files reviewed, 1 unresolved discussion (waiting on @buggmagnet)

---

ios/MullvadVPN.xcodeproj/project.pbxproj line 6443 at r2 (raw file):

				GCC_NO_COMMON_BLOCKS = YES;
				GCC_OPTIMIZATION_LEVEL = 0;
				GCC_PREPROCESSOR_DEFINITIONS = (

Could we also change the fake release schema to be a build configuration? Then we have less schemas, which I see as only a good thing. And the only thing that's different for the fake release is that the debug flag is not set.

[pinkisemils]

Works like a charm.

Reviewed 4 of 10 files at r1, 8 of 10 files at r2.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @buggmagnet)

[rablador]

Reviewed 6 of 10 files at r1, 10 of 10 files at r2, all commit messages.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @pinkisemils)

---

ios/MullvadVPN.xcodeproj/project.pbxproj line 6443 at r2 (raw file):

Previously, pinkisemils (Emīls Piņķis) wrote…

Could we also change the fake release schema to be a build configuration? Then we have less schemas, which I see as only a good thing. And the only thing that's different for the fake release is that the debug flag is not set.

Sounds good to me

[rablador]

Reviewed 8 of 8 files at r3, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved

[pinkisemils]

Reviewed 6 of 8 files at r3, all commit messages.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @buggmagnet)

---

ios/MullvadVPN.xcodeproj/project.pbxproj line 6975 at r4 (raw file):

			isa = XCBuildConfiguration;
			buildSettings = {
				ALWAYS_SEARCH_USER_PATHS = NO;

Can this be inherited from other the base config?

[buggmagnet]

Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @pinkisemils)

---

ios/MullvadVPN.xcodeproj/project.pbxproj line 6975 at r4 (raw file):

Previously, pinkisemils (Emīls Piņķis) wrote…

Can this be inherited from other the base config?

According to the documentation, we should be able to use $(inherited) to do that.
Any setting we find in this list should be overridable via xcconfig files

[rablador]

Reviewed all commit messages.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @pinkisemils)

[pinkisemils]

Reviewed 3 of 3 files at r5, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved

[pinkisemils]

, still :)

Reviewable status: complete! all files reviewed, all discussions resolved