When I remove the initial /restconf/modules check from the logic that figures out who the new leader and followers
are after isolation, those steps are passing. However, there are other REST interactions in these tests that will fail
for a similar reason.

I think at the end of all of this, we really need to understand and fix what is causing /restconf to be unresponsive.
That is too basic of a problem to ignore, and is just getting in the way of other debugging we might need to do.

For example, after skipping the /restconf call when figuring out the new leader, the test just fails when trying to use
restconf to add cars, and then again when trying to read from restconf to count how many cars are added.

If we are lucky, and this tell-based protocol is doing what we expect, then maybe this unresponsive /restconf/
issue is our only problem in this job to worry about.

example job

we did try this, and it did help somewhat as we didn't get quicker failures, but when the restconf was getting locked up (401 or 500) the csit will eventually hit the problems in some fashion
(all ODL interaction is via REST)