Upgrade script results in multiple default dedupe rules for Individual-Strict and individual-Fuzzy

In the 4.2.2 upgrade SQL, check for the condition where there are duplicate default STRICT or FUZZY dedupe rules for Individual. If this condition is found, then we know it was caused by the 4.1 upgrade and we can correct it by setting is_default = 0 to the rule with the higher ID (this will be the rule that was inserted by the 4.1 upgrade).

NOTE: We don't have to worry about unsetting is_default for a rule that was configured that way by the administrator since if any edit / create rule action is done in the UI then the duplicate is_default condition is corrected by the code.

— Original Post -----
Upgrade script creates new default dedupe rules. This was done so that "the new default rules use highly optimized SQL queries to resolve dedupes" ( dlobo & dgg on IRC, guys who know! )

However, the previous default dedupe rules are still marked as default. In addition, although the new dedupe rules less resource intensive, they may not be the deduping that administrators want.

The attached patch sets these new rules as 'not default' instead of as 'default', allowing administrators to decide if they would like to accept the new rule.