Ogury: port new adapter from Go

[zxPhoenix]

🔧 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?

New Ogury adapter (Port PR from PBS-Go)
#3700

🧠 Rationale behind the change

Why did you choose to make these changes? Were there any trade-offs you had to consider?

🔎 New Bid Adapter Checklist

• verify email contact works (I believe this happened go-side. this is a port)
• 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?
Unit tests with decent coverage

🏎 Quality check

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

[CTMBNara]

Add more tests that cover scenarios:

• impWithOguryParams + site.publisher.id + impWithoutOguryParams
• invalid impWithOguryParams + site.publisher.id + impWithoutOguryParams
• impWithoutOguryParams
• imp.tagId copied from imp.id
• price tests (for each edge case)
• test that checks imp.ext fields aren't lost, and new fields are added/replaced by impExtBidderHoist fields