new feature to send tracking requests for AI bots server side

[diosmosis]

Description

Feature related changes:

• Add two new settings: track AI bots and track AI bots using ESI (edge side includes).
• Implement server side AI bot tracking when no caching plugin is used.
• Implement server side AI bot tracking when a WordPress advanced cache is used.
• Display warning when .htaccess is used to serve cached files, since server side tracking cannot be done when this is used.
• Implement server side AI bot tracking that uses edge side includes to track AI bots when using a CDN or HTTP server that supports it (eg, Cloudflare or Litespeed web server).
• When AI bot tracking is enabled, add client side JS that will set a cookie if the current browser supports JavaScript. This cookie is only set for known AI bot crawlers. When the cookie is detected server side, we avoid sending a server side tracking request. This avoids, but does not eliminate, duplicate requests when an AI bot executes JavaScripts.
• When AI bot tracking is enabled, add recMode=2 to tracking URL client side so AI assistants that execute JS will automatically be detected by Matomo's tracking backend.
• Add notification in AI bots reporting page if AI bot tracking is not enabled, linking to MWP settings.

Minor changes:

• When calling wp_remote_request, catch exceptions just in case, and log without a fatal error, as is done with a WP_Error object.
• Forward the current user agent in tracking requests.
• Use non blocking server side tracking requests.
• Add ability to specify patches to prefixed core files.

Local environment changes:

• Add new service to docker compose that launches the Litespeed enterprise web server. Requires a serial number for a paid subscription saved to a file locally.

Checklist

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

Review

• Functional review done
• Potential edge cases thought about (behaviour 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
• New documentation added or existing documentation updated

[textagroup]

Confirmed branch ran locally as well as confirming new settings are available