Separate connect/read timeouts in pylinkahead.ini

Summary

Addresses https://gitlab.indiscale.com/caosdb/customers/f-fit/management/-/issues/93 / https://gitlab.com/linkahead/linkahead-pylib/-/issues/127
It is now possible to set separate connect/read timeouts or timeout None in pylinkahead.ini.

Corresponding Test-MR: caosdb-pyinttest!86 (merged)

Focus

• Is the CustomValidator an acceptable solution to the validation of tuples as array?
• Are there any cornercases where this breaks a request that I missed?

Test Environment

Manual Testing

Check List for the Author

• All automated tests pass
• Reference related issues
• Up-to-date CHANGELOG.md (or not necessary)
• Up-to-date JSON schema (or not necessary)
• Appropriate user and developer documentation (or not necessary)
• Annotations in code (Gitlab comments)

Check List for the Reviewer

• I understand the intent of this MR
• All automated tests pass
• Up-to-date CHANGELOG.md (or not necessary)
• Appropriate user and developer documentation (or not necessary)
• The test environment setup works and the intended behavior is reproducible in the test environment
• In-code documentation and comments are up-to-date.
• Check: Are there specifications? Are they satisfied?

src/linkahead/connection/connection.py

@@ -422,8 +422,10 @@ def configure_connection(**kwargs):
         - "keyring"  Uses the `keyring` library.
         - "auth_token" Uses only a given auth_token.
 
-    timeout : int
+    timeout : int, tuple, or None
         A connection timeout in seconds. (Default: 210)
+        If a tuple is given, they are used as connect and read timeouts
+        respectively, timeout None disables the timeout.
 
     ssl_insecure : bool
         Whether SSL certificate warnings should be ignored. Only use this for