feat(poly check): verbose output without duplication, with coloring

Changing the output of the poly check --verbose.

Details in #292 and #291

feat(poly diff): changed bricks when the Polylith Workspace is in a subfolder of the repo

Add support for monorepos with the Polylith Workspace in a subfolder.

Before, the poly diff command would fail finding any changes, because of the mismatch between the underlying git diff and the workspace folder stucture.

Details in #289

fix: allow Python 3.8 in Hatch build hook

Details in #285

feat(poetry plugin): add support for upcoming Poetry PEP 621 projects

Adding support for the upcoming Poetry release - that will be PEP 621 compliant - for those Poetry projects that will use the PEP 621 standard to define project metadata and dependencies.

Details in #278

fix: Typo in the CLI README

Details in #276

fix(cli): typo in the poly sync annotation for the --verbose option (BREAKING)

Changing the data type from str to bool for the --verbose option of the poly sync command. The str annotation is a typo, the option is meant to be a boolean just like in other commands.

NOTE: this will be a breaking change, for any users using the poly sync --verbose option today. My appologies if this is the case 🙏 . Hopefully this will be a minor thing to adjust (i.e. just use --verbose without any string value).

Details in #275

fix(uv workspaces): check if the root lock-file is workspace enabled before picking member dependencies

Check if the root lock-file is workspace enabled, before trying to find any member dependencies. Fixing issues introduced with the new uv workspaces support.

Details in #272

fix: normalize uv workspace member names before lookup

Fixing an issue with project names and uv workspaces.

Details in #270 and #269

feat(uv workspaces): add support for using a shared workspace lock-file

Adding support for the uv workspaces feature, and the shared lock-file in specific. This feature is specific for uv users and is added in the Polylith CLI.

Details in #269

feat(poly check, poly libs): use strict mode when dependencies origin from lock file

Run poly check and poly libs in strict mode when the collected third-party depencencies is collected from a lock-file.
This will have the same effect as when running the commands with the --strict option.

Details in Pull Request #268