feat(targets): Allow users to disable schema validation in targets

[edgarrmondragon]

Related:

• Closes feat: Option to disable schema validation in targets #1904

---

📚 Documentation preview 📚: https://meltano-sdk--2208.org.readthedocs.build/en/2208/

[codspeed-hq]

CodSpeed Performance Report

Merging #2208 will not alter performance

_{Comparing edgarrmondragon/feat/setting-validate-schema (cd19613) with main (32f3dec)}

Summary

✅ 6 untouched benchmarks

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (32f3dec) 88.46% compared to head (cd19613) 88.47%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2208      +/-   ##
==========================================
+ Coverage   88.46%   88.47%   +0.01%     
==========================================
  Files          54       54              
  Lines        4716     4722       +6     
  Branches      917      919       +2     
==========================================
+ Hits         4172     4178       +6     
  Misses        383      383              
  Partials      161      161              

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

[anden-akkio]

Imagine our surprise when we're figuring out how to do this and it turns out you guys merged something two weeks ago! Appreciate the implementation @edgarrmondragon and team, keep up the great work!

Context -- our use case is that we'd rather go through with an import even if the data doesn't match up perfectly with the schema, as we have downstream things that let our users clean up their data, making it often still a salvageable circumstance. We'd rather get an imperfect import than the import not going through at all! We also like fast imports and avoiding validation gets us out of a lot of CPU cycles :)