Deprecate and remove local hot standby mode

Tarantool has a local hot standby mode, in which it automatically reads the WAL of the master and continuously tries to bind to the master port. When it has successfully connected to the master port, it assumes that it has become a master.
We need to implement a similar logic in the "remote hot standby" mode, to reuse the same functionality in local and remote cases.
After that we can remove local hot standby mode.

- add a switch that the server doesn't write any replication data received from the master to its local binary log (dynamic)
- add a switch that the server, on failure to bind to the primary port, doesn't abort, but tries again and again until succeeded.