Allow annotations migration to work with both option and annotations tables

[michalkleiner]

Description

As a security enhancement in core, annotations are being moved from the option table to their own annotations table. The class AnnotationList is also being removed as not needed, so that can be used as the deciding factor which way of migration to use.

Keeping the use statement for the removed AnnotationList class is ok in PHP.

Issue No

Relates to matomo-org/matomo#23564 and DEV-13979.

Checklist

• [✔] Tested locally
• [✔] New test case added/updated?
• [NA] Are all newly added texts included via translation?
• [NA] Are text sanitised properly? (Eg use of v-text v/s v-html for vue)
• [NA] Version bumped?

[snake14]

Thank you @michalkleiner . I think the changes look good. Would you be able to adjust the tests to cover the new table when it's present?

[michalkleiner]

@snake14 updated the migration to report the number of found annotations and the migration test to check for the number of migrated items when the AnnotationList class doesn't exist.

[michalkleiner]

AI assistant referrer test failures addressed in a separate PR.

[snake14]

Thank you Michal. The changes look good to me 👍

Apologies for the delay in my review.

Edit: I left 1 comment with a question.

[snake14]

As this checks whether the class is present, I think that it's safe to merge before the core PR. Do you agree @AltamashShaikh ?