Drop tree.service config parameter

[KirillovDenis]

Currently, the tree service in node listens the same port as the object service so we can drop the tree.service config param.

But we have to think about something like a pool for tree-service clients in s3. To start we can use the first node endpoint from the peers config section

[alexvanin]

I expect that tree-service will be a part of NeoFS API one day, then it will be a part of the SDK Client and SDK Pool, so the issue will be solved. Until then, I think manual tree service endpoint specification is better than having random picking from the list of pool endpoints.

[alexvanin]

Blocked by SDK adoption.