Extend anonymisation settings to allow them to be site specific

[michalkleiner]

Description:

Reuse the anonymisation vue component from global settings within site settings to configure anonymisation options per site.

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

[michalkleiner]

I don't think the TagManagerTeaser UI test failure is related to changes here.

[nathangavin]

The CNIL stuff looks pretty good, but I think there is a little too much introduced complexity into the settings classes, they are meant to only retrieve db data and compare to policy, so I wouldn't worry about handling backup global values from inside the settings classes.

[nathangavin]

The CNIL stuff looks pretty good, but I think there is a little too much introduced complexity into the settings classes, they are meant to only retrieve db data and compare to policy, so I wouldn't worry about handling backup global values from inside the settings classes.

Reviewed and discussed with @michalkleiner, I am happy with the CNIL-related changes.

changes applied and final review done by Marc