[refine] Client - simple request-response communication

[mdabrowski1990]

Requires

#78
#22
#72

Description

As a user, I want to have an option to send diagnostic request via physical or functional addressing, so I could decide the recipients of the request.
As a user, I would like to receive all the diagnostic responses received to diagnostic request (either physically or functionally addressed), so I could easily communicate with any server.
As a user, I would like to wait till timeout or the first (and the only) response message (to this request) in case of physically addressed request, so I do not waste time as I do not expect more responses.
As a user, I would like to wait till timeout in case of functionally addressed request, so I gather all potential responses as number of receipients (and potential responses) is unknown in this case.

NOTE: This includes support only to the first response to diagnostic request (e.g. in case of request with SID 0x2A or 0x86). The client shall detect whether the response message (either by RSID or SID data prameter in case of negative response message) relates to the transmited message.

Test Strategy

Unit Tests:

• 100% code coverage

Integration Tests:

• GIVEN Client is configured, WHEN I send a simple request and responses to other requests are received, THEN responses to other requests are filtered out and not returned to the user (regardless if this is an error case or not).
• GIVEN Client is configured, WHEN I send a simple request via physical addressing and response is received THEN the response is immediately returned to the user.
• GIVEN Client is configured, WHEN I send a simple request via physical addressing and no response THEN the method is executed till timeout and error is raised.
• GIVEN Client is configured, WHEN I send a simple request via functional addressing and responses are received THEN the all the responses are returned to the user after the timeout occurs.
• GIVEN Client is configured, WHEN I send a simple request via functional addressing and no responses are received THEN nothing is returned to the user when the timeout occurs.

System Tests:

• GIVEN Client is configured with real CAN bus, WHEN I send a simple request (e.g. DiagnosticSessionControl, TesterPresent or unsupported request) via physical addressing, THEN the received response are returned to the user.
• GIVEN Client is configured with real CAN bus, WHEN I send a simple request (e.g. DiagnosticSessionControl, TesterPresent) via functional addressing, THEN all the responses is received are returned to the user.
• GIVEN Client is configured with real CAN bus, WHEN I send a unsupported request via functional addressing, THEN no response is returned to the user.

Acceptance Criteria

• Client code is updates and provides all described functionalities
• Documentation of this feature is available for the user in ReadTheDocs
• 100% test coverage for provided functionalities
• system tests on CAN are prepared, executed and passsing