[GingerNinja-STFC]

Summary

Adds a new ui.auto_confirm_alliance_contribution setting (default false) that
skips the confirmation popup shown when contributing to an alliance that has already
reached level 60. When enabled, the warning is answered with "Yes" automatically and
the contribution goes through without interruption.

How it works

The level-60 warning is shown through the game's shared MessageBox API. Its callback
(AllianceContributionViewController.<>c__DisplayClass72_0.<RequestAction>b__0) only
proceeds on MessageBox.ButtonResult.Yes (value 3, verified against the client
disassembly). Rather than installing new hooks, the existing shared
MessageBox.Show/MessageBox.ShowWithCallback detours now recognize this callback
(via IsAllianceContributionMaxLevelWarning()) and — when the setting is enabled —
invoke it directly with Yes instead of showing the popup.

Implementation notes

• The detours behind this patch now own two auto-confirm behaviors (Forbidden Tech
  upgrades and the alliance contribution warning), so the patch entry label was
  renamed from ForbiddenTechConfirm to MessageBoxConfirmations. This is cosmetic;
  the installer, hook set, and the existing [patches] forbiddentechconfirmhooks
  toggle are unchanged, so existing user configs are unaffected.
• Hook installation stays unconditional (gated only by the existing [patches]
  install toggle, default on). The ui.auto_confirm_alliance_contribution feature
  setting is checked inside the hook; when it is disabled, the native popup behavior
  is preserved exactly.
• The default (false) keeps stock behavior; the setting is opt-in, mirroring
  auto_confirm_ft_upgrade and auto_confirm_reveal_ability.
• example_community_patch_settings_en.toml updated with the new setting (other
  locales left untouched per repo convention).

Testing

• xmake -y mods builds clean on macOS (arm64, debug, --target_minver=14.6)
• git diff --check passes; no whitespace/conflict artifacts
• macOS in-game verification: setting off → warning shows as usual; setting on →
  warning suppressed and contribution applied (also sanity-check that other
  MessageBox popups — event ads, store offers, generic OK/Cancel dialogs — are
  unaffected)
• Windows build and runtime testing still needed — the MessageBox detours and
  the ButtonResult.Yes (= 3) constant should be verified against the Windows
  client (_WIN32/_M_X64), and the popup should be exercised in-game with the
  setting both off (native warning appears) and on (warning is skipped, the
  contribution registers normally)