Cerberus api uses client.toml for internal rpc connections

[dswiatek]

Cerberus API uses client.toml for internal connections to rpc port.

Generally "external" api port is defined in app.toml under [api] section and this setting works fine. Service bounds to the address and port from this setting.
But unexpected behaviour of the api appears when we used non standard ports. It occurs that internally api (as the wrapper for rpc) uses port for calling rpc from client.toml.

I think it should be treated as a bug. Client.toml should be only used for setting the behaviour of binary when it is used as client app, not for server settings.