Properly test that we do not prematurely initialize our OPTIONS

[rtibbles]

Summary

• Currently our test for no premature initialization of OPTIONS is undercut by pytest-django loading Django settings, which initialize Kolibri's OPTIONS object
• Get around this by making tests in our root test/ folder run without the pytest-django plugin
• Then move the cli import test into this folder

References

Follow up to #8372 to try to prevent us getting into that state again!

Reviewer guidance

Does the separation of tests make sense?

---

Testing checklist

• Contributor has fully tested the PR manually
• If there are any front-end changes, before/after screenshots are included
• Critical user journeys are covered by Gherkin stories
• Critical and brittle code paths are covered by unit tests

PR process

• PR has the correct target branch and milestone
• PR has 'needs review' or 'work-in-progress' label
• If PR is ready for review, a reviewer has been added. (Don't use 'Assignees')
• If this is an important user-facing change, PR or related issue has a 'changelog' label
• If this includes an internal dependency change, a link to the diff is provided

Reviewer checklist

• Automated test coverage is satisfactory
• PR is fully functional
• PR has been tested for accessibility regressions
• External dependency files were updated if necessary (yarn and pip)
• Documentation is updated
• Contributor is in AUTHORS.md

[bjester]

My initial concern was that the second execution would overwrite the code coverage, but seems that's what --cov-append addresses.

[rtibbles]

We're also not actually reporting our code coverage - it gets messed up because of our conditional test runs.