Add circulation/hold matchpoint ID to action.circulation and action.hold_request tables

[Steve Callender]

This is a wishlist item for Evergreen.

Add the config.circ_matrix_matchpoint ID that was used to successfully allow a circulation straight to a text field on the action.circulation table the same way the duration_rule, recurring_fine_rule, and max_fine_rule. Not only would this allow quick identification on the back-end to what rule was used when any given circulation was created, but it could also be pulled into the staff client so that staff can quickly identify the rule straight from the circulation record.

Likewise add the hold config.hold_matrix_matchpoint ID to the action.hold_request table for the same reasons above.

One benefit to this would be to easily run a report of how many policies were used in any given time period, and perhaps which policies are not being used at all and can be either removed or tweaked.

[Jason Boyer (jboyer)]

This is a great idea, though rather than a single id it will almost certainly have to be an array of ids since the 4 required values to process a circ can come from 1 - 4 or more ccmm rows. That may make running reports harder since I'm not sure there are any good ways to address arrays in the reporter beyond using the "contains" operator as if it's a string.