fix(jenkins): pin python kubernetes version to fix recent breakage in tests

[james-garner-canonical]

Description

Pin python kubernetes version to fix recent breakage in jenkins tests.

The latest update to the python kubernetes library (v31, 3 days ago) breaks the Jenkins github-check-merge-juju-python-libjuju test due to failure to build a new dependency (durationpy).

I thought this might be the fix for issue #1088, but that's been open since August 9. Should we switch to stricter dependency versioning across the board here to avoid breakages of this nature? In setup.py, 4 dependencies now specify both minimum and maximum versions, 5 only specify a minimum, and 2 have no version specification. In tox.ini, only 1 dependency (kubernetes) specifies a (maximum) version. tox.ini should probably have the same version constraints as setup.py.

QA Steps

All tests pass, except for integration tests, which are flaky (see issue #1108).

[dimaqq]

+1 to plug this quickly if it works.

it would be nice to know what library change made the difference, but that can be handled separately

[james-garner-canonical]

it would be nice to know what library change made the difference

The failure is when trying to build a wheel for durationpy.

ERROR: Could not build wheels for durationpy, which is required to install pyproject.toml-based projects

durationpy doesn't use the newer pyproject.toml, instead using setup.py (and a number of deprecation warnings are emitted in jenkins for its setup.py too).

[james-garner-canonical]

Integration tests are failing on this PR, but I'm not sure what the status of these integration tests is. I made a test PR against main (#1107) where the only change is adding my name to CONTRIBUTORS, and integration tests fail there too. Seven tests fail in each PR, one is different in each. I've run the integration tests twice on each PR.

Six failures are in common across both PRs (both runs):

FAILED tests/integration/test_application.py::test_upgrade_local_charm - juju...
FAILED tests/integration/test_model.py::test_deploy_bundle_with_overlay_as_argument
FAILED tests/integration/test_model.py::test_deploy_bundle_with_multiple_overlays_with_include_files
FAILED tests/integration/test_application.py::test_app_relation_destroy_block_until_done
FAILED tests/integration/test_model.py::test_wait_for_idle_with_not_enough_units
FAILED tests/integration/test_model.py::test_wait_for_idle_more_units_than_needed

Unique to this PR (one of the two runs only):

FAILED tests/integration/test_model.py::test_unit_annotations - asyncio.excep...

Unique to dummy PR [#1107] (both runs):

FAILED tests/integration/test_application.py::test_upgrade_local_charm_resource

I'm going to rerun the integration tests and see if they have the same results.

[james-garner-canonical]

See issue #1108 for a table of test failures.

[james-garner-canonical]

/merge