Add an end to end test for UDP-over-TCP on port 80

[buggmagnet]

This PR adds an end to end test that connects to a relay using UDP-over-TCP obfuscation on port80.
The test also verifies using packet capture that the traffic sent to the relay during its course is happening exclusively on port 80 using a TCP connection.

The PR also fixes an innocent mistake in DetailsView.swift and makes the chevron icon accessibility tap action actually expand the connection details.

---

This change is 

[linear]

IOS-942 Add end-to-end test for udp-to-tcp port selection

[SteffenErn]

Reviewable status: 0 of 5 files reviewed, 1 unresolved discussion

---

ios/MullvadVPNUITests/RelayTests.swift line 199 at r1 (raw file):

        let streamFromPeeerToRelay = try XCTUnwrap(
            capturedStreams
                .filter { $0.destinationAddress == connectedToIPAddress }.first

Is it enough to check that one stream on port 80 exists or does it make sense to verify that no other stream on a different port exists?

[buggmagnet]

Reviewable status: 0 of 5 files reviewed, 1 unresolved discussion (waiting on @SteffenErn)

---

ios/MullvadVPNUITests/RelayTests.swift line 199 at r1 (raw file):

Previously, SteffenErn (Steffen Ernst) wrote…

Is it enough to check that one stream on port 80 exists or does it make sense to verify that no other stream on a different port exists?

The way the packet capture API was designed is not immediately obvious.
There will be 1 Stream object exactly, that we capture here by filtering by connectedToIPAddress

As the router that does the capture is used by multiple teams, we only want to bother about the relay our device has connected to.
In a nutshell, this is only stream we care about here.

[SteffenErn]

Reviewable status: 0 of 5 files reviewed, 1 unresolved discussion (waiting on @buggmagnet)

---

ios/MullvadVPNUITests/RelayTests.swift line 199 at r1 (raw file):

Previously, buggmagnet wrote…

The way the packet capture API was designed is not immediately obvious.
There will be 1 Stream object exactly, that we capture here by filtering by connectedToIPAddress

As the router that does the capture is used by multiple teams, we only want to bother about the relay our device has connected to.
In a nutshell, this is only stream we care about here.

Ok, thanks for the clarification :)

[github-actions]

🚨 End to end tests failed. Please check the failed workflow run.

[github-actions]

🚨 End to end tests failed. Please check the failed workflow run.