Made Width and Depth compatible in current version of the tracer

[DmitryVasilevsky]

Tracer component now produces compatible "Width" and "Depth" metrics, both computed in the depth counter. "Width" previously computed by the width counter is still reported as "QubitCount". User can request width or depth optimized circuit to get compatible width and height in desired case. For example,

using(q = Qubit()) { T(q); }
using(q = Qubit()) { T(q); }

will result in Width=1, Depth=2 when OptimizeDepth is false, and Width=2, Depth=1 when OptimizeDepth is true. For compatibility "QubitCount" is kept and will still be reported as 1.

[bettinaheim]

The failing iqsharp build seems to be due to a test that simply needs to be updated.

[cgranade]

Thanks for opening this! I think the main thing that jumps out at me as a user of the trace simulator is that, as per @bettinaheim's comments, it's not really clear what ExtraWidth is and what that metric tracks about the execution of a quantum program.

[bettinaheim]

Thanks for adding this!