Code review comment for lp:~mskalka/juju-ci-tools/assess-destroy-model

Ok. I restructured the test a little to reflect what you think is the proper procedure and swapped to json at your recommendation.

Now it:
boostraps and stores that as a ModelClient object
adds a model which is captured as a new ModelClient object
destroys that model using that object
lists model so we know we avoid bug 1505504
switches back to the original model using our first client object
runs list-model on that client object to try to catch that timing hole

I confirmed the test fails on 2.0-beta8; it throws a called process error on list-models which is the expected outcome. It passes on current juju versions.