Fix TypedConstraint equality check

[ericj-db]

Resolves #1081

Description

It looks like the root cause behind #1081 is because of how we determine equality between TypedConstraint objects. During incremental runs, we rely on the equality check to determine which constraints to drop or apply

dbt-databricks/dbt/adapters/databricks/relation_configs/constraints.py

Lines 30 to 32 in 6981678

	def get_diff(self, other: "ConstraintsConfig") -> Optional["ConstraintsConfig"]:
	# Find constraints that need to be unset
	constraints_to_unset = other.set_constraints - self.set_constraints

The current default equality check is considering fields like warn_unenforced. This does not work because this is a user supplied config that has no meaning when we are creating a TypedConstraint from existing Databricks relations. The Fix is to override the __eq__ to match the __hash__ which already ignores such fields

Checklist

• I have run this code in development and it appears to resolve the stated issue
• This PR includes tests, or tests are not required/relevant for this PR
• I have updated the CHANGELOG.md and added information about my change to the "dbt-databricks next" section.

[benc-db]

Wow, great job!

[github-actions]

Coverage report

Click to see where and how coverage changed

File	Statements	Missing	Coverage	Coverage (new stmts)	Lines missing
dbt/adapters/databricks
constraints.py
Project Total

This report was generated by python-coverage-comment-action

[Korijn]

Awesome, happy to see the regression test as well! 🚀

[Korijn]

I installed dbt-databricks from this branch and tested locally; this issue seems to be fixed. 🎉