Added a minimal rogue client detection mechanism at the transport level

[mrsuciu]

Proposed changes

Clients that behave rogue by repeatedly sending invalid messages in a certain interval of time are now tracked and blocked from connecting for a predefined amount of time. Time calculations are independent of system time.

Related Issues

• Fixes #

Types of changes

What types of changes does your code introduce? Put an x in the boxes that apply. You can also fill these out after creating the PR.

• [ ] Bugfix (non-breaking change which fixes an issue)
• [x] Enhancement (non-breaking change which adds functionality)
• [ ] Test enhancement (non-breaking change to increase test coverage)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected, requires version increase of Nuget packages)
• [ ] Documentation Update (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• [ ] I have read the CONTRIBUTING doc.
• [ ] I have signed the CLA.
• [ ] I ran tests locally with my changes, all passed.
• [ ] I fixed all failing tests in the CI pipelines.
• [ ] I fixed all introduced issues with CodeQL and LGTM.
• [ ] I have added tests that prove my fix is effective or that my feature works and increased code coverage.
• [ ] I have added necessary documentation (if appropriate).
• [ ] Any dependent changes have been merged and published in downstream modules.

Further comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

[codecov[bot]]

Codecov Report

Attention: Patch coverage is 18.08511% with 77 lines in your changes missing coverage. Please review.

Project coverage is 55.25%. Comparing base (3672ebe) to head (97da591). Report is 9 commits behind head on master.

Files with missing lines	Patch %	Lines
...tack/Opc.Ua.Core/Stack/Tcp/TcpTransportListener.cs	14.44%	72 Missing and 5 partials :warning:

Additional details and impacted files

```diff @@ Coverage Diff @@ ## master #2850 +/- ## ========================================== - Coverage 57.23% 55.25% -1.98% ========================================== Files 352 352 Lines 75520 67427 -8093 Branches 15988 13822 -2166 ========================================== - Hits 43223 37258 -5965 + Misses 27870 26082 -1788 + Partials 4427 4087 -340 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

---

🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests

[romanett]

@mrsuciu tests fail on some pipelines: The active test run was aborted. Reason: Test host process crashed : Unhandled exception.Unhandled exception. System.NullReferenceException: Object reference not set to an instance of an object. at Opc.Ua.Bindings.TcpTransportListener.OnAccept(Object sender, SocketAsyncEventArgs e) in /_/Stack/Opc.Ua.Core/Stack/Tcp/TcpTransportListener.cs:line 761 at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)

[mrsuciu]

@mrsuciu tests fail on some pipelines: The active test run was aborted. Reason: Test host process crashed : Unhandled exception.Unhandled exception. System.NullReferenceException: Object reference not set to an instance of an object. at Opc.Ua.Bindings.TcpTransportListener.OnAccept(Object sender, SocketAsyncEventArgs e) in /_/Stack/Opc.Ua.Core/Stack/Tcp/TcpTransportListener.cs:line 761 at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)

@romanett This did not happen on my local runs, but somehow the test machines running the tests do not provide IP Addresses.

[mregen]

Hi @mrsuciu, I would only chose a less offending name than RogueClient, e.g just ClientTracker or ClientActivity etc. and make sure there are not too many info messages.