This pull request adds native support for the Nativo bidder to the codebase, moving it from a generic alias-based configuration to a dedicated, fully integrated bidder module. The changes include the implementation of the Nativo bidder logic, configuration, schema, and integration tests, as well as the removal of the old alias-based approach.

Nativo Bidder Integration:

• Implemented the NativoBidder class, handling bid requests and responses, bid extension updates, and error handling. (NativoBidder.java)
• Defined the Nativo-specific impression extension model ExtImpNativo. (ExtImpNativo.java)
• Added a dedicated configuration class for Nativo, including dependency injection and usersyncer setup. (NativoConfiguration.java)
• Created a Nativo-specific bidder configuration file. (nativo.yaml)
• Added a JSON schema for validating Nativo bidder parameters. (nativo.json)

Testing and Documentation:

• Added integration tests for the Nativo bidder, including request/response fixtures. (NativoTest.java, test-auction-nativo-request.json, test-auction-nativo-response.json, test-nativo-bid-request.json, test-nativo-bid-response.json) [1] [2] [3] [4] [5]

Configuration and Cleanup:

• Removed the Nativo alias configuration from the generic bidder config and related test properties, fully switching to the dedicated Nativo adapter. (generic.yaml, test-application.properties, PbsConfig.groovy, BidderParamsSpec.groovy) [1] [2] [3] [4] [5]

These changes ensure that Nativo is now a first-class, configurable bidder in the system, with dedicated code, configuration, validation, and tests.

Schema validation:

• Introduced a new JSON schema file nativo.json to define and validate the parameters accepted by the Nativo adapter.

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

Adding optional property "placementId" to Nativo Adapter
Adding SDK Renderer Version in Response

🧠 Rationale behind the change

We have already been using this property, but it wasn't correctly documented in the adapter.
Our mobile ad formats need the Prebid Renderer name and version to work.

🔎 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 all the necessary tests.

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