<!--
Explain what problem this PR addresses
-->

This PR and this cloudquery/cloudquery#2459 should ensure logs and stdout are not running over each other.

The convention should be the following fmt.Print* -> stdout, logs -> stderr
this way it's easy to turn off one stream or the other depending on the need

If we continue the resolving after PreRR error, more (this time type based) errors are generated from the column resolvers that expect a certain type.

#### Summary

Found a nasty hang when context was cancelled. Still need to add some tests for that to catch regression.

This adds checks for a whole range of misconfigurations that could happen in the tables config.

Some of the main cases handled:
 - invalid table name
 - wildcard in skip_tables section
 - child table specified without its parent table
 - list of tables is empty

Closes cloudquery/cloudquery#2312

This also adds quite needed tests for our scheduler

🤖 I have created a release *beep* *boop*
---


## [0.12.8](v0.12.7...v0.12.8) (2022-10-07)


### Bug Fixes

* Error on incorrect table configuration ([#237](#237)) ([6ad75f5](6ad75f5))
* Exit gracefully on context cancelled ([#252](#252)) ([b4df92e](b4df92e))
* Progressbar should go into stdout ([#250](#250)) ([b8bcdad](b8bcdad))
* Recover panic in table resolver and object resolver flows ([#257](#257)) ([04dba02](04dba02))
* Stop if PreResourceResolver fails ([#251](#251)) ([ee83f8f](ee83f8f))

---
This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).