test(e2e): normalise container-augmented config fields in settings contract

`it_should_allow_admins_to_get_all_the_settings` compares the live
settings response with `env.server_settings_masking_secrets()`, which
the host loads from the same TOML the container starts from. The
container's entry script (ADR-T-009 §7) however augments that config
before the daemon comes up — when no PEM and no path is supplied for
`auth.{private,public}_key`, it defaults the key paths to
`/etc/torrust/index/auth/{private,public}.pem`, and the runtime DB
URL points at the in-container bind-mount target
(`/var/lib/torrust/index/database/...`) rather than the host path the
runner uses (`./storage/index/lib/database/...`).

The result is two fields that legitimately diverge between expected
and actual even on a green run, so the equality assertion fired on
environment plumbing rather than on real contract drift. Clear
`auth.private_key_path`, `auth.public_key_path`, and
`database.connect_url` on both sides before comparing, with a comment
explaining why each one is masked and pointing at ADR-T-009 §7. The
rest of the response — including the masked secrets the test was
originally written to cover — is still asserted byte-for-byte.

Author: peer-cat

tests/e2e/web/api/v1/contexts/settings/contract.rs

@@ -76,9 +76,28 @@ async fn it_should_allow_admins_to_get_all_the_settings() {
 
     let response = client.get_settings().await;
 
-    let res: AllSettingsResponse = serde_json::from_str(&response.body).unwrap();
-
-    assert_eq!(res.data, env.server_settings_masking_secrets().unwrap());
+    let mut actual: AllSettingsResponse = serde_json::from_str(&response.body).unwrap();
+    let mut expected = env.server_settings_masking_secrets().unwrap();
+
+    // Normalise environment-specific fields that legitimately differ
+    // between the host-side loader (which builds `expected` from the
+    // shipped TOML plus the host's env overrides) and the container's
+    // effective configuration (which the entry script may augment —
+    // e.g. defaulting `auth.{private,public}_key_path` to
+    // `/etc/torrust/index/auth/{private,public}.pem` when neither
+    // PEM nor path is supplied; ADR-T-009 §7). The DB connect URL
+    // similarly differs because the container path
+    // (`/var/lib/torrust/index/database/...`) is the bind-mount
+    // target of the host path the test runner uses
+    // (`./storage/index/lib/database/...`).
+    actual.data.auth.private_key_path = None;
+    actual.data.auth.public_key_path = None;
+    actual.data.database.connect_url.clear();
+    expected.auth.private_key_path = None;
+    expected.auth.public_key_path = None;
+    expected.database.connect_url.clear();
+
+    assert_eq!(actual.data, expected);
 
     assert_json_ok_response(&response);
 }