Description:

Our UI and API currently requires a password confirmation for certain (critical) actions. Currently that is done in each vue component and API in a similar way (but own implementations).

This PR introduces a new PasswordConfirmation vue component, that can be easily reused in other components. This also helps to let them look similar across Matomo. All existing password confirmations were replaced with the new component.

The password confirmation check in the API also was done in each class, but will now be available in each API, as it's part of the abstract class.

As confirming passwords introduced issues with other login plugins (that simply don't use passwords), a new event Login.userRequiresPasswordConfirmation was introduced, that allows to disable password confirmation for certain users.
If it's disabled, the API won't perform password checks and in UI the password confirm will still be displayed, but with password input disabled and an enabled submit button, so it can be submitted without entering a password.

Additionally this PR introduces password confirmations for this critical actions:

On Privacy > Anonymize data page it is possible to change the settings for purging old log data and reports as well as directly purging such data. As this is a critical action, that can cause data loss, we will now require the password to be confirmed.

fixes #19335
fixes #19169
fixes https://github.com/matomo-org/matomo-security/issues/209

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