allow disabling move to top functionality

[wbbradley]

Hello, thanks for the great work with autoimport! This PR implements a bit of functionality I've been missing in autoimport, which is to allow users (through configuration) to disable the "move to top" feature.

Rationale

I am working in an large codebase that has several areas of circular dependencies, and at this stage, it is not a priority to detangle that mess. I understand and appreciate the value of "code as a DAG", however in this instance I'd still like to be able to leverage the other functionality in autoimport without having to prioritize cycle breaking in my project.

This issue has been raised here.

Checklist

• Add test cases to all the changes you introduce
• Update the documentation for the changes

[lyz-code]

Hi @wbbradley thanks for the PR.

I don't either have time right now to fix the issue sorry :(, you will probably be able to solve the issue by running make update

[lyz-code]

Alternatively you can disable the check in the CI if you want as I feel it's more important the easiness in contribution than the security

[coveralls]

Pull Request Test Coverage Report for Build 9886215236

Details

• 7 of 7 (100.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.09%) to 95.808%

---

Totals
Change from base Build 9029820318:	0.09%
Covered Lines:	320
Relevant Lines:	334

---

💛 - Coveralls

[wbbradley]

I've gone ahead and bumped the versions of mkdocs and commitizen, and I've ignored the specific vulnerability found in the prior run but left all other checks running. Thanks for your help, and again, thanks for autoimport. Let me know if there are other steps I can take care of to help get it pushed up to pypi. And, I'm totally open to feedback on anything I did here. Mostly just tried to get my use-case unblocked.

[lyz-code]

Thank you so much for the contribution (✿◠‿◠)