Inconsistent field naming

[typerat]

The documentation for fetchAndJoinCustomAudience shows the field user_bidding_signals in snake case. The respective field when accessed from the bidding JS is userBiddingSignals in camel case (which took weeks to figure out, see #90).

This is specifically causing problems, as we have to use two different representations for a custom audience in our system - one for CA management and a different one for bidding - and make sure we use the correct one in each instance.

All other fields that I checked are in snake case, as expected.

[syntxerror]

Hey @typerat. We're compiling a list of the fields that need to updated as you've pointed out and will hopefully have the change put in soon to use a singular case.