Canonicalize multilingual special-page aliases and surface proxy block hints

[Copilot]

Special-page protection only matched the configured name form, which could miss requests arriving through localized aliases. This change canonicalizes special-page names from the request path/title and exposes the content-language aliases on denied responses so reverse proxies can block equivalent URLs consistently.

• Canonicalize multilingual special-page names

  • Normalize configured protected special pages through SpecialPageFactory::resolveAlias()
  • Resolve the incoming request title to the canonical special-page name before protection checks
  • Keep matching case-insensitive and prefix-agnostic (Special:, localized namespace names, alias forms)

• Surface proxy-facing alias metadata

  • Add X-CrawlerProtection-Special-Page-Aliases on denied special-page responses
  • Include the canonical Special: title plus known content-language aliases for that page
  • Preserve existing denial behavior; this only adds machine-readable alias hints for front-facing filters

• Wire alias resolution through services

  • Inject SpecialPageFactory and content language into CrawlerProtectionService
  • Keep hook handling thin and leave normalization/alias expansion in the service layer

• Regression coverage

  • Add unit coverage for:
    • canonicalizing configured localized aliases
    • canonicalizing request titles before denial
    • emitting the alias header
  • Extend integration coverage to assert the new denial header on protected special pages

Example:

$wgCrawlerProtectedSpecialPages = [ 'Spezial:Linkliste' ];

A request for either of these will now resolve to the same protected canonical page:

Special:WhatLinksHere
Spezial:Linkliste

And denied responses include:

X-CrawlerProtection-Special-Page-Aliases: Special:WhatLinksHere, Spezial:Linkliste

• Fixes [Feature request] Support for multilingual special page translations #18

[Copilot]

Copilot was unable to review this pull request because there is no eligible user to bill. To allow Copilot reviews on bot-authored pull requests, enable direct organization billing in your organization's Copilot settings.

[Copilot]

Copilot was unable to review this pull request because there is no eligible user to bill. To allow Copilot reviews on bot-authored pull requests, enable direct organization billing in your organization's Copilot settings.