opt: add cancellation checks to expensive exploration rules

[DrewKimball]

#85041 added some cancellation checks to the optimizer. However, there are a few exploration rules that can take significant time to complete for complex queries - for example, ReorderJoins can take a long time when the join limit is increased and/or join properties are expensive to calculate, and GenerateLookupJoins is expensive when there are many candidate indexes. We should consider adding cancellation checks to the following rules, as well as their variants (if any):

• ReorderJoins
• GenerateMergeJoins
• GenerateLookupJoins
• GenerateConstrained/Limited/IndexScans
• GenerateZigzagJoins

Jira issue: CRDB-19428