MDL-57791 analytics: Changes after review

- Split model::predict in parts
- JS promises updated according to eslint-plugin-promise
- New API methods replacing direct DB queries
- Reduce insights nav link display cost
- Increase time limit as well as memory for big processes
- Move prediction action event to core
- Dataset write locking and others
- Refine last time range end time
- Removed dodgy splitting method id to int
- Replace admin_setting_predictor output_html overwrite for write_setting overwrite
- New APIs for access control
- Discard invalid samples also during prediction

lib/mlbackend/php/classes/processor.php

@@ -176,7 +176,7 @@ class processor implements \core_analytics\predictor {
      *
      * During evaluation we need to shuffle the evaluation dataset samples to detect deviated results,
      * if the dataset is massive we can not load everything into memory. We know that 2GB is the
-     * minimum memory limit we should have (\core_analytics\model::increase_memory), if we substract the memory
+     * minimum memory limit we should have (\core_analytics\model::heavy_duty_mode), if we substract the memory
      * that we already consumed and the memory that Phpml algorithms will need we should still have at
      * least 500MB of memory, which should be enough to evaluate a model. In any case this is a robust
      * solution that will work for all sites but it should minimize memory limit problems. Site admins