Filter data in tests

[amishas157]

PR Checklist

PR Structure

• This PR has reasonably narrow scope (if not, break it down into smaller PRs).
• This PR avoids mixing refactoring changes with feature changes (split into two PRs
  otherwise).
• This PR's title starts with the jira ticket associated with the PR.

Thoroughness

• This PR adds tests for the most critical parts of the new functionality or fixes.
• I've updated the docs and README with the added features, breaking changes, new instructions on how to use the repository.

Release planning

• I've decided if this PR requires a new major/minor/patch version accordingly to
  semver, and I've changed the name of the BRANCH to release/* , feature/* or patch/* .

What

In our effort to optimize tests, this PR:

• Adds filters in test for incremental models
• Remove unique tests for certain models as they are already defined unique in SQL config. Example:

stellar-dbt-public/models/marts/ledger_current_state/trust_lines_current.sql

Lines 1 to 8 in c4c96d3

	{{
	config(
	tags = ["current_state"],
	materialized = "incremental",
	unique_key = "unique_id",
	cluster_by = ["asset_code", "asset_issuer"]
	)
	}}

Why

To optimize test runs and make pipelines robust

Known limitations

None. Tested on Test airflow

[chowbao]

nit: I'm pretty sure the accepted_values test can be removed. This field is a boolean (only possible values are true, false, null) and there is already a not_null check

[amishas157]

Where would boolean check be enforced though? Is there a schema validator? I think bigquery should be able to enforce it