Fix for #180: passing the entity ID to the custom hook when deleting a custom value

[jaapjansma]

Overview

When deleting a custom value record from a multiple custom data set. The entityId is not passed to the hook civicrm_custom. This causes some weird behaviours in extensions (for example CiviRules, see: https://github.com/CiviCooP/org.civicoop.civirules/issues/208

See https://lab.civicrm.org/dev/core/issues/180

Before

Upon deleting a custom value $entityID parameter of the hook civicrm_custom is not set.

After

Upon deleting a custom value $entityID parameter of the hook civicrm_custom is set to the right value..

[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]

As a general rule I'm against adding extra db queries just for the sake of hooks (since it's a performance hit and those hooks are seldom used) but in this case I'd give it a +1 since a delete is not that common and it would improve consistency.

[jaapjansma]

Thanks for merging. I totally agree we should keep the sql statements down for performance.