administration: workaround alarm.getLastActiveProcess not during alarm execution

At this point, the alarm is active, but active process for this activity
was not created yet. By passing include_active, the latest active
process will be returned (not the previous one)

Honnestly, not sure if this falls into workaround or non documented
normal use case for include_active=True.

bt5/erp5_administration/SkinTemplateItem/portal_skins/erp5_administration/Alarm_activateCheckConsistency.py

 kw = {}
 
 if context.getProperty('incremental_check'):
-  last_active_process = context.getLastActiveProcess()
+  last_active_process = context.getLastActiveProcess(include_active=True)
   if last_active_process is not None:
     kw['indexation_timestamp'] = {
         'query': last_active_process.getStartDate(),