Add ability to mock an RSocket connection within unit tests to isolate functionality to one end of an RSocket connection for testing.

Motivation

Without the ability to mock an RSocket connection in unit tests, unit tests effectively become integration tests. The (current) necessity to create both RSocket client and server within a unit test adds a large amount of indirectly-related code that falls outside of the scope of testing one end of the connection and its functionality.

Desired solution

Provide a mechanism to mock an RSocket connection.

Considered alternatives

Current solution is to create and configure both ends, RSocket client and server, prior to testing an RSocket client. This adds a considerable amount of code to even a simple test and reduces the clarity and concision of the test.

Additional context

N/A