Clarify types on `hook_custom` and `hook_customPre`

#2636 - Authx - Undefined function in drupal 9 

Prevent adding duplicate dashlet if present with same name and label

APIv4 Entity.get refactor to be more efficient

Cleanup references to old dedupe class names

#2486 Add ACLEntityRole APIv4 Entity

Add DedupeRule, DedupeRuleGroup and DedupeException API4 entity

[php8-compat] Fix undefined property on Array Cache class in wordpres…

[REF][php8-compat] Further fixes where there is a required paramater …

translation#67 - Define "Translation" table. Add during installation/upgrade.

APIv4 - Cleanup getFields, add @internal flag for non-public field attributes

Remove some unused variables

[php8-compat][REF] Fix php8 error on undefined constant CIVICRM_DISAB…

The custom & customPre hooks are not called elsewhere in gituniverse
so we can add type hints and fix casting & comments to make it
clearer what the variables are

The previous comments reflected a developmental iteration.

5.38

[php8-compat][NFC] Ensure that the 2nd parameter of hash_equals is a …

5.38.0 release notes: added late changes

Afform - Fix custom field handling and add tests

Extract code that populates temp table for an individual group

APIv4 - Fix getFields to respect default_value from getFields

GetFields had an odd way of setting defaults for field metadata;
this reuses the default_value property instead for more internal consistency.

This ensures custom fields are handled properly by Afform,
including multi-record custom field groups & their autogenerated blocks,
and contact reference fields.

Remove pass-by-ref as param not altered

This makes Entity.get more efficient - it no longer does a file scan when getting one or more entities by name.
Also deprecates the includeCustom param which was redundant with the where clause.
This is the first APIv4 param to be deprecated - added handling to emit a warning when using a deprecated param
and hide deprecated params in the APIv4 explorer.

[php8-compat][phpunit8][NFC] Fix PHPUnit Warnings and fix a php error on f…

This creates an entity, `Translation` (`civicrm_translation`), to represent a single translated database value. Loosely speaking,
any field in the database can be designated as translatable -- and then it will be permitted to store values like:

```sql
INSERT INTO civicrm_translation (entity_table, entity_id, entity_field, language, string)
VALUES ('civicrm_event', 100, 'title', 'fr_FR', 'La nouvelle chaine')
```

This is based on a `civi-data-translate` strings table, but with some changes:

* Entity names are usually singular, but `String` is conflicted. I previously used hybrid
  String/Strings (depending on context), but we negotiated `Translation` on tcon.
* The language only needs 5 characters (NN_nn).
* Consolidated `bool is_active` and `bool is_default` into one `int status_id`.
* Added indexing
* Mark dynamic foreign key

This commit includes the BAO with some of the backing-methods required for
API exposure.  However, the API won't really work until we have the
validation-values event, so the API has been kicked to a subsequent PR.

The list of translatable entities/fields will be signficant because it will
determine when/how to redirect data in API calls.  This patch does not
commit to specific translatable fields - but it does provide a hook to
determine them.

When the API PR becomes unblocked, it will include test-coverage that hits the API, BAO, and hook.