Improve handling of deactivating incompatible plugins during update

[sgiehl]

Description:

Incompatible plugins are currently deactivated within the initial process performing the update.
This can cause random problems, as at this point disabling a plugin might trigger other code causing to process a mix of old and new code, which can cause random errors being displayed.

To be sure that won't happen anymore we should deactivate the plugins within the second request, which is processed with new code only.

Review

• Functional review done
• Potential edge cases thought about (behavior of the code with strange input, with strange internal state or possible interactions with other Matomo subsystems)
• Usability review done (is anything maybe unclear or think about anything that would cause people to reach out to support)
• Security review done
• Wording review done
• Code review done
• Tests were added if useful/possible
• Reviewed for breaking changes
• Developer changelog updated if needed
• Documentation added if needed
• Existing documentation updated if needed

[bx80]

This looks like a fairly straightforward change, I can't see any obvious issues with disabling the plugins in the second phase 👍

[michalkleiner]

Looks ok to me as a code change. In terms of the process I can't judge where it's better.