This solves the issue when multiple plugins are being
executed on these 2 events. If a plugin really needs
to be executed after the page cache plugin it can still
use \Joomla\Event\Priority::MIN for its own event handler.

This solves the issue when multiple plugins are being
executed on these 2 events. If a plugin really needs
to be executed after the page cache plugin it can still
use \Joomla\Event\Priority::MIN for its own event handler.

…' into feature/cache-plugin-refactor

…in-refactor

I left the $app protected to prevent static code
analysers from concluding that the property must be
removed because it's never set. This wrong detection is
the consequence of the way CMSPlugin detects and sets
this property through Reflection.

# Conflicts:
#	plugins/system/cache/cache.php