Extend Optable Targeting API request forming with additional parameters

[justadreamer]

Motivation

Feature completeness of the Targeting API support in the SDK.

Details

The current implementation does not allow passing arbitrary identifiers and other params - thus is not complete to spec, documented here: https://docs.optable.co/optable-documentation/admin/real-time-api/api-integrations-guide/optable-targeting-api

The Targeting Request construction should accept arbitrary IDs as defined per spec and privacy parameters.
By default consent data including strings should be obtained from the standard IAB-defined locations in the UserDefaults.

Objective

1. Implement the prerequisite generic API call parametrization Rework Optable Real-time APIs configuration and request forming #49
2. Extend Targeting interface to accept additional parameters (s.a. various IDs and privacy params)
3. Rework request construction
4. Improve response processing into a convenient data structure to be used with the Prebid SDK - this is likely to be the primary enrichment target.
5. Implement unit test coverage for the request forming and ideally against the mock server to check response parsing if any.
6. Update the example app to configure a Targeting call and enrich the Prebid SDK call.