APIv4 - Read & write contact primary and billing locations as implicit joins

[colemanw]

Overview

Makes it easier to search and display contact primary email, phone, im without using any joins in SearchKit.
Both read & write are supported.
See dev/core#3659

Before

In SearchKit, you must add an explicit join if you want to view a contact's address, phone, email, etc.

After

Declares an implicit join between the contact record and primary/billing email, phone, address & im records, making it easier to retrieve those directly from the Contact API.
Read and write both supported. Also you can pass NULL to delete them.

[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).

[eileenmcnaughton]

@colemanw so the expectation is that if the contact has a street address & I update address_primary.postal_code it will NOT overwrite the full primary address (I think that is OK but it could be argued either way)

[eileenmcnaughton]

In my testing I find that for get

$contacts = \Civi\Api4\Contact::get()
  ->addSelect('address_billing.street_address', 'address_billing.postal_code', 'address_billing')
  ->addWhere('id', '=', 55)
  ->execute();

Returns the following

I find the returning of an id for address_billing odd - but I'm sure you have previously advised me there is precedent for that.

For create and update I do NOT see anything advertised in the api explorer for them

[eileenmcnaughton]

While not api advertised it seems the update does work

CRM.api4('Contact', 'update', {
  values: {"address_billing.street_address":"Household"},
  where: [["id", "=", 55]]
})

[eileenmcnaughton]

I don't think the explorer thing is blocking - & I think the update behaviour for address is consistent with v3 so I think this is probably fine

[eileenmcnaughton]

On reflection I'm going to merge this so it hits the rc - I know you were wanting it to & we could update the rc with the outcome of any further discussion is need be