Prioritization strategies

[katelashkevich]

@PowerMaxZ

For every target activity in the transitions with WT due to prioritization, we need to identify what prioritization strategy is applied in that activity. More specifically, we need to identify:

1. activities in which prioritization is applied (i.e., target activities);
2. frequency of prioritization (i.e., percent of cases for which prioritization is applied from the total number of cases processed in the activity);
3. prioritization rule (i.e., which cases are prioritized based on the case attributes and the resource). Here, we look for statistically significant correlations between the prioritization occurrence and the case attributes per resource (because different resources could apply different prioritization strategies). If not possible to identify per resource, then we look for a general strategy applicable regardless of the resource. If no confident correlation is identified, the result is 'no rule.'
4. prioritization rule quality. To assess the quality of the identified rule, we use the metrics of confidence and support.

We could probably re-use this code https://github.com/AutomatedProcessImprovement/prioritization-discovery for implementing this ticket. I'm not sure since I was not involved in this research. Please see if this code could provide us with the prioritization rules in some form. If it could (even if not exactly as I described in the ticket), let us use it to save time and effort.

The requirements for the UI for this component will be specified in a separate ticket.

FYI
Here, we also need to know which resources apply prioritization and how much WT due to prioritization each of them induces in each transition. This is already available in Kronos.