SERVER-139003Open
Report specific join optimization fallback reasons from singleTableAccessPlans()
Every failure in {{singleTableAccessPlans()}} is reported as {{failedToGetSingleTableAccessViaCBR}} by the executor. That includes: * planning or CBR errors * CBR accepting several plans it can't rank * the single plan CBR can't estimate (SERVER-138000) SERVER-134637 will add another: falling back when a node's chosen plan uses a hashed, wildcard or collated index. These cases look the same in serverStatus and {{{}$queryStats{}}}. Consider having {{singleTableAccessPlans()}} return a