**What this PR does / why we need it**:
**Which issue(s) this PR fixes**:
We saw a spike in divide by zero panics in the code introduced in #7769.
I was able to reproduce this error via a test that calculates
`WeightedParallelism` with a start that's after the end. Not sure if
this is possible, but we definitely saw this happening in our ops
environment, so something is causing it, and the fix should guard
against it in any case.
**Special notes for your reviewer**:
**Checklist**
- [X] Tests updated
Co-authored-by: Sandeep Sukhani <sandeep.d.sukhani@gmail.com>
// If totalDur is 0, the query likely does not overlap any of the schema configs so just use parallelism of 1 and
// let the downstream code handle it.
iftotalDur==0{
level.Warn(logger).Log("msg","could not determine query overlaps on tsdb vs non-tsdb schemas, likely due to query not overlapping any of the schema configs,"+
"letting downstream code handle it gracefully","start",start,"end",end)