New adapter: HypeLab

[Minebomber]

🔧 Type of changes

• new bid adapter
• bid adapter update
• new feature
• new analytics adapter
• new module
• module update
• bugfix
• documentation
• configuration
• dependency update
• tech debt (test coverage, refactorings, etc.)

✨ What's the context?

This PR adds the HypeLab bid adapter to Prebid Server Java.

The adapter supports site banner, native, and video inventory. It accepts property_slug and placement_slug bidder params, forwards eligible OpenRTB 2.6 requests to HypeLab, adds HypeLab display manager metadata, and maps HypeLab bid responses back into Prebid bid types.

🧠 Rationale behind the change

HypeLab needs a dedicated adapter because the request is not just a raw OpenRTB pass-through. The adapter validates required bidder params, sets tagid from placement_slug, preserves the HypeLab bidder ext, adds provider metadata, and resolves response bid type from mtype, ext.hypelab.creative_type, VAST markup, or the original impression media type.

🔎 New Bid Adapter Checklist

• verify email contact works
• NO fully dynamic hostnames
• geographic host parameters are NOT required
• direct use of HTTP is prohibited - implement an existing Bidder interface that will do all the job
• if the ORTB is just forwarded to the endpoint, use the generic adapter - define the new adapter as the alias of the generic adapter
• cover an adapter configuration with an integration test

🧪 Test plan

How do you know the changes are safe to ship to production?

• Added unit coverage for request creation, required param validation, mixed valid/invalid impressions, response parsing failures, empty responses, and bid type resolution.
• Added integration coverage for the /openrtb2/auction path and HypeLab adapter configuration.
• Ran ./mvnw -Dtest=HypeLabBidderTest test successfully.
• Generated a local JaCoCo report for HypeLabBidder: 96% instruction coverage and 97% line coverage.

🏎 Quality check

• Are your changes following our code style guidelines?
• Are there any breaking changes in your code? No breaking changes.
• Does your test coverage exceed 90%?
• Are there any erroneous console logs, debuggers or leftover code in your changes? No.