🥳 Beta 1 of dbt utils 1.0.0 🥳

🔜 we're aiming to release the final version in late October (post-Coalesce, alongside dbt Core 1.3) 📆

Scrappy upstart no longer, dbt utils 1.0 is a major milestone.

Following on from the discussions in #487, this release tightly focuses the project on user-facing tests and convenience macros. Experimental materializations and cross-database macros have moved to the experiments repo and dbt Core respectively.
In 1.0, we are finally implementing a flurry of long-promised deprecations and knotty bugs to create a cleaner, tidier, stabler API that people can build against well into the future. We have chosen to collate all of the breaking changes into one hit; after this, functionality in dbt utils 1.0.0 will work in all subsequent 1.x.y (if you don't know about semantic versioning, this is a good time to read up on it!)

Add not_empty_string test by @epapineau in #634
Many tests can now be validated against subgroups of a table, thanks to @emilyriederer in #633

Remove table argument from unpivot() by @miles170 in #671
Remove varargs in surrogate_key and safe_add, in favour of a single fields list argument by @miles170 in #674
Remove group_by and relation_alias from deduplicate macro, make order by mandatory by @miles170 in #673
Totally remove the identifier macro (use adapter.quote() instead) by @miles170 in #672
Remove not_null_where and unique_where by @joellabes in #678

🚨 Treat blank strings differently to nulls in surrogate_key (#488). 🚨
- This one could cause trouble. We are going to default to correct behaviour going forward, but if you have a surrogate key which depends on the old incorrect behaviour, you will be able to opt back into it.
Fully delete all the cross-database macros that have moved to dbt Core.

Full Changelog: 0.9.2...1.0.0-b1