poetry: disable keyring in tests

[xxyzz]

The tests would fail in CI when keyring is enabled

The Failed to unlock the item! error message in this pr #109777 (comment) is from https://github.com/jaraco/keyring/blob/977ed03677bb0602b91f005461ef3dddf01a49f6/keyring/backends/SecretService.py#L70-L74 or https://github.com/jaraco/keyring/blob/977ed03677bb0602b91f005461ef3dddf01a49f6/keyring/backends/libsecret.py#L59-L78

The tests probably don't need keyring, so disable it should be fine.

• Have you followed the guidelines for contributing?
• Have you ensured that your commits follow the commit style guide?
• Have you checked that there aren't other open pull requests for the same formula update/change?
• Have you built your formula locally with brew install --build-from-source <formula>, where <formula> is the name of the formula you're submitting?
• Is your test running fine brew test <formula>, where <formula> is the name of the formula you're submitting?
• Does your build pass brew audit --strict <formula> (after doing brew install --build-from-source <formula>)? If this is a new formula, does it pass brew audit --new <formula>?

---

[xxyzz]

Why it's building the build system(["hatchling", "hatch-vcs", "hatch-fancy-pypi-readme"]) of the "jsonschema" package?

[SMillerDev]

Because it's a dependency

[iMichka]

I'm trying something else, bumping the resources: #110433

[xxyzz]

I'm trying something else, bumping the resources

I guess the builds success in your pull request is because brew test-bot runs different build commands. Maybe updating dependencies will fix the test error.

[iMichka]

#110433 Fixed it :)

[xxyzz]

Not sure if you still want to merge this to solve the Python CI error but I guess if I create a new pull request it'll fail to build again.