Make sure that guard selection algorithm handles restriction-based behavior correctly
We want to avoid a recurrence of tor#40876 (closed) here; to do so, we need to make sure that our guard selection algorithm obeys restrictions in the particular way described in torspec!182 (merged), possibly as amended by torspec!184 (merged). (We should wait until the dust settles on those MRs a bit, of course.)