Add pytest test suite

[jensens]

Summary

• Add comprehensive pytest test suite with 113 tests covering all modules
• Add test infrastructure: [project.optional-dependencies], [tool.pytest.ini_options], [testenv:test] in tox
• All shared utilities at 100% coverage, 75% overall
• Tests use tmp_path fixtures and unittest.mock to avoid real subprocess/git calls

Coverage breakdown

Module	Coverage
shared/ (utils, packages, path, call, git)	100%
multi_call.py	100%
re_enable_actions.py	88%
pep_420.py	76%
config_package.py	68%
Overall	75%

Test plan

• uv run --extra test pytest -v — 113 tests pass
• uv run --extra test pytest --cov=plone.meta — 75% coverage
• No real subprocess calls (git/tox/gh) are executed during tests
• Review test structure and mocking patterns

🤖 Generated with Claude Code

[gforcada]

Before looking at the code, I'm not sure how worth it is to add a test suite to these set of scripts really...

The code is in a state that only minimal changes and fixes are being done and very few new features are added, and those would probably break plenty of tests which might or might not be that useful.

Anyway, I wanted to give this first impression before reviewing the code.

[gforcada]

Nice job, and I'm specially grateful that you used some AI to generate them, as I find them not that useful in practice, but as you did not have (hopefully) to spend too much time on it, then it is not too bad.

I'm +1 on the test_shared ones, but rather +0 to -1 for the test_config_package.py tests, as they might be quite brittle to maintain as we evolve the script.

[jensens]

Do we need testing this? As you noticed I am exploring to work with AI agents on code. Having tests is the only sane way to have a verification loop there and catch regressions. And for humans it doe not hurt too.