tt replicaset status: no clear error when incorrect orchestrator is forced

[p7nov]

tt replicaset status shows a huge scary error trace when called with an explicit orchestrator that doesn't match the real orchestrator used on the cluster.

Environment: Ubuntu, tt-ee 2.2.1, Tarantool EE 3.0.0

Steps to reproduce:

1. Create a vshard app from template, build it, and start.
2. Check a replica set status forcing an incorrect orchestrator --cartridge:

$ tt rs status shard-app/ --cartridge

Expected result: Concise and clear error message that the selected orchestrator is not used on the cluster

Actual result: A huge scary error stack trace takes up the entire screen. Here's a fragment: