Refactor `mullvad-relay-selector`

Implement a system built on 'queries' for selecting appropriate relays.
A query is a set of constraints which dictates which relay(s) that *can*
be chosen by the relay selector.

The user's settings can naturally be expressed as a query. The semantics
of merging two queries in a way that always prefer user settings is
defined by the new `Intersection` trait.

Split `mullvad-relay-selector` into several modules:

- `query.rs`: Definition of a query on different types of relays. This
module is integral to the new API of `mullvad-relay-selector`
- `matcher.rs`: Logic for filtering out candidate relays based on a
query.
- `detailer.rs`: Logic for deriving connection details for the selected
relay.
- `tests/`: Integration tests for the new relay selector. These tests
only use the public APIs of `RelaySelector` and make sure that the
output matches the expected output in different scenarios.

1 files changed, 1 insertions, 1 deletions

diff --git a/talpid-future/Cargo.toml b/talpid-future/Cargo.toml
index 1245fe1e2a..9baa0245d1 100644
--- a/talpid-future/Cargo.toml
+++ b/talpid-future/Cargo.toml
@@ -15,5 +15,5 @@ rand = "0.8.5"
 talpid-time = { path = "../talpid-time" }
 
 [dev-dependencies]
-proptest = "1.4"
+proptest = { workspace = true }
 tokio = { workspace = true, features = [ "test-util", "macros" ] }