.NET: Thin 3.0: Test timeout is too short

In a log from https://ci.ignite.apache.org/buildConfiguration/ApacheIgnite3xGradle_Test_RunNetTests/7024431?hideProblemsFromDependencies=false&hideTestsFromDependencies=false&pluginCoverage=true&expandBuildTestsSection=true (attached to this ticket) the following can be seen:

[12:06:40] :  [dotnet test]   Passed TestReplaceExact [65 ms]
[12:06:42] :  [dotnet test] Jan 24, 2023 11:06:42 AM io.scalecube.cluster.membership.MembershipProtocolImpl lambda$onDeadMemberDetected$42
[12:06:42] :  [dotnet test] INFO: [default:org.apache.ignite.internal.runner.app.PlatformTestNodeRunner_2:2f32f38d-529d-4d6f-92c7-a0b05d92475e@172.120.0.8:3345] Member leaved without notification: default:org.apache.ignite.internal.runner.app.PlatformTestNodeRunner:db118c3f-14cc-4b63-a0b8-e0a2cdf3cd2e@172.120.0.8:3344... skipped ...[12:06:43] :  [dotnet test] INFO: Node added to the logical topology [node=org.apache.ignite.internal.runner.app.PlatformTestNodeRunner]
[12:06:46] :  [dotnet test] [11:06:46] [Info] [ClientFailoverSocket] Primary socket connection lost, reconnecting.... skipped ...[12:06:46] :  [dotnet test]   Failed TestContains [6 s]
[12:06:46] :  [dotnet test]   Error Message:
[12:06:46] :  [dotnet test]    System.TimeoutException : The operation has timed out.

Looks like a node left and returned back (a probable reason for leaving is a GC pause), but it took a few seconds because it's guided by timeouts. So it seems that the timeout of 5 seconds is too low in Dotnet tests, it should be probably set to a higher value.