Configure Member's RPC connection settings via Control API (#27)

[evdokimovs]

Part of #27

Synopsis

We need to add configuration of the idle_timeout, reconnect_timeout and ping_interval by Control API. This settings can be configured in Member element spec. If no settings provided into spec, default values from the config will be used.

Solution

• 1. Add reconnect_timeout, idle_timeout and ping_interval fields into specs
• 2. Use this fields in the WsSession
• 3. Add unit and E2E tests for this functional
• 4. Add this fields into e2e-demo's Control API UI

Checklist

• Created PR:
  • In draft mode
  • Name contains WIP: prefix
  • Name contains issue reference
  • Has k:: labels applied
  • Has assignee
• Documentation is updated (if required)
• Tests are updated (if required)
• Changes conform code style
• CHANGELOG entry is added (if required)
• FCM (final commit message) is posted
  • and approved
• Review is completed and changes are approved
• Before merge:
  • Milestone is set
  • PR's name and description are correct and up-to-date
  • WIP: prefix is removed
  • All temporary labels are removed

[evdokimovs]

FCM

Configure Member's RPC connection settings via Control API (#95, #27)

- add 'idle_timeout', 'reconnect_timeout' and 'ping_interval' to Member spec in Control API
- add RPC connection configuration fields to the 'e2e-demo' and 'medea-control-api-mock'

[tyranron]

@evdokimovs please, polish the docs accross the project a bit more better, without loosing current context.

[tyranron]

@evdokimovs hyperium/tonic#314 is resolved as .gitignore comment suggests, and tonic 0.2 is out.

I've checked using Config::compile_well_known_types, but, as reffered in docs, it requires now to specify .proto files for well-known types by ourselves and doesn't use prost-types anymore. This is absolutely not something intended for resolving this issue.

If so, I suggest just to delete this empty generated file manually in build.rs and that's it!