Vdc api is over reliable tcp channel. No need to retry.
The delay for inactive reply with retrying was 15s. That is too much for UI configurator, it uses timeout 12s. Inactive reply is returned after 5s now.
This change fixes #17725.
There is more that can be done in this area:
- Vdcd knows instantly that the device is not present, but there is no way in vdv api to reply to ping with inactive reply.
- Vdsm shall not ask whether the device is preset when vdcd already sent message that the device is inactive.
ref #17725