QaTool: Add config override handler and fix payment product mapping

[whooooop]

What was done

• Added a CONFIG_OVERRIDE action handler in QaToolPlatformBridge. The bridge now accepts a { type: 'platform', action: 'config_override', options: {...} } postMessage at runtime and merges the incoming options into this._options via a shallow top-level merge. No acknowledgement is sent back; configFileModule is not modified. Because modules read options through the bridge.options getter without caching, the override propagates immediately.

• In _paymentsGetProductsPlatformData and _paymentsGetProductPlatformData: replaced hardcoded string literals 'playgama' and 'qa_tool' with PLATFORM_ID.PLAYGAMA / PLATFORM_ID.QA_TOOL constants. Added product[PLATFORM_ID.QA_TOOL] spread on top of product[PLATFORM_ID.PLAYGAMA] so that qa_tool-specific fields take priority over the playgama base config. Reduced _paymentsGetProductPlatformData to a one-liner that reuses the result of _paymentsGetProductsPlatformData(), removing duplicate merge logic.

Changed files

• src/platform-bridges/QaToolPlatformBridge.js — config override handler, payment product mapping deduplication and qa_tool override priority