Track AI Bots through our HTTP Tracking API

[sgiehl]

Description:

Checklist

• [✔] I have understood, reviewed, and tested all AI outputs before use
• [✔] All AI instructions respect security, IP, and privacy rules

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

[sgiehl]

Note: We need to update the tracking documentation afterwards. I'll create a PR for that once this PR has an approval.

[michalkleiner]

Purely looking at the changes since Marc's latest review, there's just one more place where we can use the logger interface mechanism instead of Common::printDebug.

I'd have one more question on top of that and that is whether it's ok to limit the deletion to 25000 records. Is that sufficient, or would we need to run the call in a loop until there's nothing to delete?

[caddoo]

I've tested this manually locally, works as expected the existing tracking of course works as well.

I like the BC approach, simple.

Just a couple questions that aren't blocking.

stale