Add CI check to prevent circular dependencies from being introduced

[andygrove]

Is your feature request related to a problem or challenge?

We were unable to publish version 36.0.0 to crates.io due to a circular dependency (https://github.com/apache/arrow-datafusion/issues/9277).

We have seen a similar issue in the past (https://github.com/apache/arrow-datafusion/issues/7281)

To avoid this in the future, it would be nice to add some checks for this in CI.

Describe the solution you'd like

I do not have a proposal for how to achieve this. I am hoping there is some existing cargo tooling out there.

Describe alternatives you've considered

No response

Additional context

No response