avoid allowing incompatible version of maison to coexist with autoimport

[wbbradley]

A recent major version bump of maison is causing autoimport to fail at runtime because it claims to support maison>1.4.0.

Checklist

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

[coveralls]

Pull Request Test Coverage Report for Build 10933727782

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 95.808%

---

Totals
Change from base Build 9895668044:	0.0%
Covered Lines:	320
Relevant Lines:	334

---

💛 - Coveralls

[spazm]

Including this example of the error message displayed when maison 2.0.0 is installed.
Hoping this helps surface the details for anyone else who runs into this problem before the fix is pushed to pypy. See also #258 and #260

% autoimport
Traceback (most recent call last):
  File "/usr/local/bin/autoimport", line 5, in <module>
    from autoimport.entrypoints.cli import cli
  File "/lib/python3.12/site-packages/autoimport/entrypoints/cli.py", line 12, in <module>
    from maison.config import ProjectConfig
ImportError: cannot import name 'ProjectConfig' from 'maison.config' (/lib/python3.12/site-packages/maison/config.py)

[lyz-code]

Closing as duplicate of https://github.com/lyz-code/autoimport/pull/260