fix conflict for real not minimal snowplow tracker

[akurdyukov]

From #8719

Closes #8719

Problem

Instaling dbt-core with meltano in the same virtualenv breaks dbt because contract conflict between minimal-snowplow-tracker (dependency of dbt) and snowplow-python-tracker.

Solution

Adds explicit version check and use minimal or full contract call.

Checklist

• I have read the contributing guide and understand what's expected of me
• 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
• This PR has no interface changes (e.g. macros, cli, logs, json artifacts, config files, adapter interface, etc) or this PR has already received feedback and approval from Product or DX

[cla-bot]

Thanks for your pull request, and welcome to our community! We require contributors to sign our Contributor License Agreement and we don't seem to have your signature on file. Check out this article for more information on why we have a CLA.

In order for us to review and merge your code, please submit the Individual Contributor License Agreement form attached above above. If you have questions about the CLA, or if you believe you've received this message in error, please reach out through a comment on this PR.

CLA has not been signed by users: @akurdyukov

[graciegoheen]

Hey - thanks so much for opening this up! Is there is a reason you targeted the 1.4.latest branch? We typically target the main branch and backport as needed.

[dbeatty10]

Temporarily added Skip Changelog label so that we can see if this passes the CI checks (minus the check for a changelog).

This label should be removed prior to final review + merge.

[akurdyukov]

Hey - thanks so much for opening this up! Is there is a reason you targeted the 1.4.latest branch? We typically target the main branch and backport as needed.

Yes, I needed get it working with dbt-clickhouse which is compatible with 1.4 only. I can open new PR to main after I fix build errors.

[akurdyukov]

I'm not sure if it's correct but I fixed mypy error by ignoring.

[graciegoheen]

Hey @akurdyukov - I tried to re-point this PR to the main branch, but got a handful of merge conflicts. Would you be able to take a look? Thanks!

[github-actions]

This PR has been marked as Stale because it has been open with no activity as of late. If you would like the PR to remain open, please comment on the PR or else it will be closed in 7 days.

[edgarrmondragon]

@graciegoheen do you think this PR can be salvaged or is it better to start a fresh one targeting main?

[dbeatty10]

@graciegoheen do you think this PR can be salvaged or is it better to start a fresh one targeting main?

@edgarrmondragon A fresh one targeting the main branch seems like the way to go here.

In the meantime, I switched this PR back to targeting the 1.4.latest branch to make it easier to see the original diff.

[seunggs]

Is there any progress on this @edgarrmondragon? Running into the same issue working with Meltano + dbt

[edgarrmondragon]

Is there any progress on this @edgarrmondragon? Running into the same issue working with Meltano + dbt

@seunggs I got #9528 started

[dbeatty10]

Thanks for doing that @edgarrmondragon 🙏

Closing this one in favor of #9528

[seunggs]

@edgarrmondragon Thank you for the update 🙏 Will track that issue!