Fix bug in primary handling where TRUE rather than 1 used

[eileenmcnaughton]

Overview

Fixes a bug where ensuring valid primary addresses relies on is_primary being 1 or 0 but NOT TRUE of FALSE

Before

Updating a phone (etc) results in other phones for the contact being updated to is_primary = 0

civicm_api3('Phone', 'create', ['is_primary' => 1, 'id' => 50);

but this does not

civicm_api3('Phone', 'create', ['is_primary' => TRUE, 'id' => 50);

After

Both variants trigger is_primary cycle.

Technical Details

When a phone (etc) is updated to have is_primary = 1 then all the other phones for that contact should be is-primary = 0

Comments

@colemanw Note apiv4 still bypasses primary handling, for address at least

[civibot]

(Standard links)

• If this is your first pull-request for CiviCRM, please browse CONTRIBUTING.md for information about the development and testing processes.
• If you are reviewing this pull-request, you may wish to consult the test sites and the Review Standards (long template, short template).

[colemanw]

This looks reasonable to me.