Update buildkit for use with new site_email_address table

[colemanw]

This complements civicrm/civicrm-core#31909 by installing site email in the appropriate table depending on version.

[totten]

I'm a little torn. The above would be fine greenfield-wise, and it's written/tested. OTOH, I try to keep env-vars pretty stable for anyone who has a fork with their own build-type. OTOOH, this isn't a contract that we're vocal about.

The underlying issue is probably that this kind of value pushes the limits of what's intuitive/safe for processing with shell commands. (Actually, cv sql --eval has a better notation @ENV[XXX], but api3/api4 don't have an equivalent -- and api3/api4 seems seems like a nicer bridge -- eg when faced with git bisect, cv api4 OptionValue.update would endure better.)

I think I'll go ahead and merge this to keep 31909 moving. But I reserve the right to flipflop 😉 (if I find a nicer way to switch it to api4).

[colemanw]

@totten so you're saying there might be build types floating around with CIVI_DOMAIN_EMAIL="Demonstrators Anonymous" <[email protected]>?

What about just add a little regex here to extract the email part from the angle brackets?