Debug update and remove setConfig hook

[jsnellbaker]

Type of change

• Bugfix

Description of change

A re-submission of an older PR #3714 that was reverted from master via #3736.

Re-copying the description of the above ticket here for reference:

With the implementation of the new hooks library we added a ready functionality that would allow async hooks to be queued until the hooks were declared ready in pbjs.processQueue. This caused config.setConfig calls to be queued and config.getConfigs being called before pbjs.processQueue were not getting data (such as the call for printing prebid info in #3700). I updated the DEFAULT_DEBUG to be set immediately rather than relying on config.setConfig in the utils library, which I think makes a little more sense.

Also, the pbjs.setConfig hook was only being used for the pre1api module, which was removed in 2.0 so I think it's best we just remove the hook, which I've also done.

Other information

Fixes #3700 and #3997

[jsnellbaker]

Please hold on this PR - there is an issue that needs to be addressed.

[snapwich]

Added a fix. The issue is caused by us having a circular dependency between the utils module and the config module. Circular dependencies are actually allowed but if you import a reference and immediately execute it, it can cause issues with the binding's value being undefined depending on the load order (hence why all the utils.logMessage and such in config are no problem since they're not immediately called but utils.getParameterByName was an issue since it was immediately invoked).

I attempted breaking out some of the query string utilities into their own module and then just re-exporting them in the utils module (to prevent a huge refactor) however sinon apparently has issues stubbing re-exported bindings compared with regular es6 exports... Really weird.

I'm not a huge fan of this solution because I just changed config to use the url.js#parseQS function I found already in our code but the circular dependency still exists. However, since parseQS is not part of the circular dependency the issue doesn't present itself. I'm also not a fan because url.js#parseQS and utils.js#getParameterByName basically do the same thing. But I guess this is good enough for now.