Add RTB House Bid Adapter as example implementation of FLEDGE (prebid#4568)

* RTBHouse Bid Adapter: adds channel as optional param, updates bidder flags

* RTBHouse Bid Adapter: fixed table descriptions

* RTBHouse Bid Adapter: minor textual changes on bidder docs

* ortb_blocking_supported and description section

* ortb_blocking_supported and description section (#1)

* ortb_blocking_supported and description section

* rephrasing

* ORTB blocking examples update

* Javascript type for examples added

* typo fix

* code fix

* Prebid Server setup by host companies

* RTB House Bidder added as an example implementation interpretResponse with FLEDGE

---------

Co-authored-by: Leandro Otani <[email protected]>
Co-authored-by: rtbh-lotani <[email protected]>

Author: 2 people

dev-docs/modules/fledgeForGpt.md

@@ -147,7 +147,7 @@ for more details. This means that the AuctionConfig objects returned from `inter
 the request it should be associated with. This may raise the question: why isn't the AuctionConfig object returned as part of the bid? The
 answer is that it's possible to participate in the FLEDGE auction without returning a contextual bid.
 
-An example of this can be seen in the OpenX OpenRTB bid adapter [here](https://github.com/prebid/Prebid.js/blob/master/modules/openxOrtbBidAdapter.js#L327).
+An example of this can be seen in the OpenX OpenRTB bid adapter [here](https://github.com/prebid/Prebid.js/blob/master/modules/openxOrtbBidAdapter.js#L327) or RTB House bid adapter [here](https://github.com/prebid/Prebid.js/blob/8fe7115021fd348d0f3b090da48c40c095078800/modules/rtbhouseBidAdapter.js#LL135C4-L135C4).
 
 Other than the addition of the `bidId` field, the `AuctionConfig` object should adhere to the requirements set forth in FLEDGE. The details of creating an
 `AuctionConfig` object are beyond the scope of this document.