CiviMail - New autocompletes for selecting recipients

[colemanw]

Overview

When composing a mailing, this replaces the single include/exclude/groups/mailings widget with two widgets, one for include and another for exclude. Groups and mailing are still combined together in autocomplete results, but are loaded more efficiently by APIv4.

Original proposal: https://lab.civicrm.org/dev/core/-/issues/4045

Replaces #26522

Before

After

• 2 widgets on separate lines (Include/Exclude)
• Little wrench button given some text to make it more visible
• "Hidden Smart Group 123456" relabeled "Search Results"

Technical Details

Builds on #26536 and #26583 to create a SearchDisplay that UNIONS groups and mailings.

[civibot]

(Standard links)

• If you are reviewing this pull-request, you may wish to consult the test sites and the Review Standards (long template, short template).

[seamuslee001]

Jenkins re test this please

[agileware-justin]

Would be good to get rid of the almost completely useless "~ 94 recipients" text and instead replace this with a URL "Show Recipients" which links to a contact listing of the actual recipients for the mailing based on the criteria. Open in new page - similar to the Mailing report links.

Because showing some of the recipients is far less useful than showing the actual recipients.

Otherwise, definitely better than the current feature. Thanks!

[colemanw]

@agileware-justin just to keep things focused, please open a different issue for that. This PR doesn't touch that piece.

[agileware-justin]

No worries

[demeritcowboy]

This works for me.
I can no longer select null, so I can't no longer send nothing to nobody. But my set of thoughts on that is empty.

[colemanw]

Now how will @demeritcowboy get in touch with his old friend Null?

[demeritcowboy]

Ah, clever reference!

// CRM-15522 ends

Yeah, if only.

[colemanw]

// CRM-15522 lives!

[colemanw]

Even in APIv4, it lives on!

civicrm-core/Civi/Api4/Utils/FormattingUtil.php

Lines 56 to 68 in fbdb1ee

	/*
	* Because of the wacky way that database values are saved we need to format
	* some of the values here. In this strange world the string 'null' is used to
	* unset values. If we encounter true null at this layer we change it to an empty string
	* and it will be converted to 'null' by CRM_Core_DAO::copyValues.
	*
	* If we encounter the string 'null' then we assume the user actually wants to
	* set the value to string null. However since the string null is reserved for
	* unsetting values we must change it. Another quirk of the DB_DataObject is
	* that it allows 'Null' to be set, but any other variation of string 'null'
	* will be converted to true null, e.g. 'nuLL', 'NUlL' etc. so we change it to
	* 'Null'.
	*/