Revert "add conflictsWith to provider schema (#2084)"

[jrhouston]

This reverts commit 550f2c1.

Description

Acceptance tests

• Have you added an acceptance test for the functionality being added?
• Have you run the acceptance tests on this branch?

Output from acceptance testing:

$ make testacc TESTARGS='-run=TestAccXXX'

...

Release Note

Release note for CHANGELOG:

...

References

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

[wiebeck]

Now that I've just fixed all my provider configs to work with conflictsWith.... 🙄

[spkane]

This fixed an issue we ran against on Friday where we were not defining config_path anywhere, but the system would complain that it conflicted with things we were defining like host and client_key. I am assuming that the provider auto-detected something set in the environment like KUBECONFIG and was reading that in as a default config_path and then causing the conflict message to be thrown.