We should validate the zone config extension set by the user won't affect certain existing multi-region primitives.

As suggested in #83605 (review), we may want to add the following validation:

1. REGIONAL extensions don't set lease_preferences
2. REGIONAL IN extensions don't set lease_preferences that disagree with their home region. I.e. After the extension gets applied, the home region is unchanged.
3. REGIONAL IN extensions don't set replica constraints or voter contains that disagree with their home region.
4. Extensions can't break a database's survivability goal.

If we find out the user gives a zone config extension that violate the rules above, we return an error and reject the incoherent extension. We want to guide the user towards a configuration that makes sense.

Jira issue: CRDB-18004
Epic CRDB-14616