fix: poly check performance for large repos

[DavidVujic]

Description

The poly check command performs AST parsing to find any missing bricks or third-party imports. A module that already have been parsed should be cached during the session. This is done since before, but with the default max size of lru_cache. For large Polylith workspaces, the cache need to be bigger.

Motivation and Context

See discussion #354

How Has This Been Tested?

✅ CI
✅ running the poly check command for a repo with 18+ projects, 350+ bricks and with large python files (20K LOC).

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• I have read the code of conduct.
• I have read the contributing guide.
• I have updated the documentation accordingly (if applicable).

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud