[refine] Design UDS Server API #1

Requires

#48
#90

Description

As a user, I would like to have Server's API defined, so I know what functionalities are provided by server simulation and how to use them.
As a user, I want to have option to turn the server on/off so I decide when it responds and when it does not.
As a user, I want to have option to configure server with any Transport Protocol interface, so the top level interface is the same regardless of the network and lower layers configuration.
As a user, I would like to have possibility to use ResponseManager, so response messages are automatically created according to a predefined rules set.
As a user, I would like to have possibility to define list of responses to the next messages, so I could force the server to response in a desired way regardless of currently configured rules.
As a developer, I would like to have UDS Server class with methods (with annotations and descriptions) defined, so I know what has to be implemented and what functionalities would be provided by server simulation.

Acceptance Criteria

• Server class is defined.
• Each Server's method has annotation and description. There shall be no code, preferable they raise exceptions.
• Server's methods are defined to provide following functionalities:
  • Setting and reading Server configuration of session parameters (e.g. p2_server) - more details in [refine] Server - configuration #91
  • Automatic responding to incoming requests
  • Multiple response messages to one request (for example SID 0x2A and 0x86 responses - periodical or on event)