[snake14]

Description

Lets the new core:rotate-encryption-keys console command (matomo-org/matomo#25410) replace this plugin's encryption key and re-encrypt the stored Slack OAuth token with the new key. Until now, changing encryption_key in the [Slack] config section made those values unrecoverable.

The plugin declares its encrypted values through the new CoreAdminHome.getEncryptionKeyRotationTargets event, and Encryption::withKey() lets values be encrypted and decrypted with a key other than the configured one. On a Matomo version without the command, nothing changes.

Depends on matomo-org/matomo#25410.

Issue No

PG-5545

Steps to Replicate the Issue

1. Connect Slack so its OAuth token is stored, on a Matomo build that includes Add a console command to rotate plugin encryption keys matomo#25410.
2. Run ./console core:rotate-encryption-keys --plugin=Slack.
3. encryption_key in the [Slack] section of the config file has changed, and sending a Slack report or alert still works.

Checklist

• [✔] Tested locally or on demo2/demo3?
• [✔] New test case added/updated?
• [NA] Are all newly added texts included via translation?
• [NA] Are text sanitized properly? (Eg use of v-text v/s v-html for vue)
• [✔] Version bumped?
• [✔] I have understood, reviewed, and tested all AI outputs before use
• [✔] All AI instructions respect security, IP, and privacy rules
• [NA] Documentation updated?

[lachiebol]

LGTM, works well locally