Diamond-distance wildcard incorrect for leakage-aware reporting

[coreyostrove]

Describe the bug
In 0.9.14 new subspace restricted metrics were introduced as part of new reporting/modeling capabilities for measuring leakage and tailoring gauge optimization to leaky systems. These new metrics were not integrated into the diamond distance wildcard model workflow, and as a result the wildcard values obtained when constructing a leakage-aware report are pretty crazy. We should automatically detect when we're using leakage-aware analysis and switch over to subspace restricted diamond distance for that case.