Use fastjsonschema instead of jsonschema for validation

[gshank]

resolves #145

Description

For performance reasons we are replacing jsonschema with fastjsonschema.

Checklist

• I have read the contributing guide and understand what's expected of me
• I have signed the CLA
• I have run this code in development and it appears to resolve the stated issue
• I have opened an issue to add/update docs, or docs changes are not required/relevant for this PR
• I have run changie new to create a changelog entry

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 92.30769% with 2 lines in your changes missing coverage. Please review.

Project coverage is 64.78%. Comparing base (bef3b7d) to head (fdecf8c).

Files	Patch %	Lines
dbt_common/dataclass_schema.py	96.00%	1 Missing ⚠️
dbt_common/exceptions/base.py	0.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #146      +/-   ##
==========================================
+ Coverage   64.33%   64.78%   +0.45%     
==========================================
  Files          51       51              
  Lines        3230     3243      +13     
==========================================
+ Hits         2078     2101      +23     
+ Misses       1152     1142      -10     

Flag	Coverage Δ
unit	64.78% <92.30%> (+0.45%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[graciegoheen]

All the other error message look good - essentially saying X is invalid because of Y.

In the case, the invalid value '{'an_attr': 'fubar'}' is invalid because it's missing 1 or more properties. I think it's probably still helpful to name the invalid value (so users can identify where they need to go add the missing properties), so I feel good about this one as well.