feat: Allow semantic comparison of schemas

[borchero]

Motivation

Two schemas that define the same columns, with the same constraints, and the same set of the schema-level rules are generally considered equal.

Recently, I talked to @AndreasAlbertQC and @MoritzPotthoffQC about adding serialization of schemas to dataframely. This PR is a preparation to allow a schema X to be considered equal to a schema Y that is dynamically created from the serialization of X.

Changes

• Add a matches method to the Schema class. One could also implement __eq__ in the metaclass to allow for Schema == Schema to be a semantic comparison. This has a bunch of weird effects though, so I refrained from doing that.
• Implement a matches function for Column and Rule. Initially, I implemented __eq__ for them, but it feels more consistent to also implement a method named matches. It also allows to pass an additional parameter for evaluating Column equality (i.e. the name of the column) which will come in handy when performing serialization.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (8d4b41b) to head (673f3f0).
Report is 4 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main       #55   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           39        39           
  Lines         1896      1947   +51     
=========================================
+ Hits          1896      1947   +51     

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.