Adding alkimi vendor-id and user-sync url modification

[VelRaj21]

🔧 Type of changes

• [ alkimi] configuration

✨ What's the context?

This PR updates the Alkimi bidder's YAML configuration in two ways:

1. Sets the IAB GVL (Global Vendor List) vendor ID for Alkimi from the placeholder 0 to the official value 1169, which is Alkimi's
   registered vendor ID with the IAB Transparency & Consent Framework (TCF v2).
2. Extends the user-sync redirect URL to forward additional consent/privacy signals (gdpr_consent, gpp, gpp_sid) alongside the
   previously supported gdpr and us_privacy parameters.

File touched:

• src/main/resources/bidder-config/alkimi.yaml

🧠 Rationale behind the change

• vendor-id: 1169: Without the correct GVL vendor ID, Prebid Server cannot enforce TCF v2 consent decisions for Alkimi correctly — the
  bidder may be incorrectly filtered out (or incorrectly allowed through) when a user's consent string is evaluated. Setting 1169 aligns Prebid
  Server with Alkimi's IAB GVL registration so consent enforcement (purposes, legitimate interest, special features) is accurate.
  • Expanded usersync URL: The existing URL only forwarded gdpr and us_privacy to Alkimi's sync endpoint. Modern privacy frameworks require:
    • gdpr_consent — the actual TCF consent string (not just the gdpr=1/0 flag), so Alkimi can validate consented purposes on its side before
      dropping a sync cookie.
    • gpp and gpp_sid — Global Privacy Platform string and section IDs (covering CCPA, CPRA, Colorado, Virginia, etc.), enabling Alkimi to honor
      U.S. state privacy laws under the new IAB GPP framework that supersedes us_privacy for new signals.
  • Trade-offs considered: The added query parameters are populated by Prebid Server's generic usersync URL builder via standard {{macro}}
    substitution — no custom Java code or new dependencies were needed. The change is purely declarative and additive: existing sync flows that only
    passed gdpr/us_privacy continue to work because the new macros resolve to empty strings when the corresponding signals are absent.

🔎 New Bid Adapter Checklist

N/A — this is a configuration update for an existing adapter, not a new bid adapter.

🧪 Test plan

• Existing unit tests pass without modification: AlkimiBidderTest — 8 tests, 0 failures, 0 errors.
  • Existing integration test passes without modification: AlkimiTest (covers the OpenRTB2 auction round-trip against a mocked Alkimi
    exchange).
  • A repository-wide search confirmed that the changed values (vendor-id: 1169, the user-sync URL, and the new gdpr_consent/gpp/gpp_sid
    placeholders) are not asserted in any test file, so no test updates are required.
  • The {{gdpr_consent}}, {{gpp}}, and {{gpp_sid}} macros are already resolved by Prebid Server's generic usersync infrastructure
    (UsersyncerCreator and the cookie-sync flow), which is covered by existing tests (UsersyncerCreatorTest, CookieSyncHandlerTest,
    SetuidHandlerTest).
  • Manual validation: confirmed via git diff --stat src/test/ that no test files require changes.

🏎 Quality check

• Are your changes following our code style guidelines? — YAML-only change; follows the same formatting/indentation as every other bidder
  config in src/main/resources/bidder-config/.
  • Are there any breaking changes in your code? — No. The added query parameters are additive; consumers that previously received only
    gdpr/us_privacy continue to work unchanged. The vendor-id change is the correction of an unset placeholder (0) and does not alter any public
    API.
  • Does your test coverage exceed 90%? — No production Java code changed; existing AlkimiBidderTest (8 tests) and AlkimiTest (integration)
    coverage remains intact and passing.
  • Are there any erroneous console logs, debuggers or leftover code in your changes? — No. The diff is two lines in a single YAML file.