Update pre-commit

[kurtmckee]

Description

This PR resolves pre-commit deprecation warnings that are appearing in CI (recent example).

In addition, it updates the pyupgrade configuration to target Python 3.9+ compatibility, and commits the changes introduced by pre-commit run -a, and fixes the resulting flake8 complaints.

While this resolves existing deprecation warnings, I recommend updating the flake8-bugbear plugin to the latest version (you can install and run upadup to accomplish this automatically, or copy-and-paste the version shown in the console logs below). The plugin version in the pre-commit config is two years old, and new versions are throwing new warnings.

$ upadup
upadup is checking additional_dependencies of flake8...
  flake8-bugbear==22.10.27 => flake8-bugbear==24.10.31
apply updates...done

$ pre-commit run -a
compute_endpoint/globus_compute_endpoint/endpoint/config/config.py:188:13:
B028 No explicit stacklevel argument found.
The warn method from the warnings module uses a stacklevel of 1 by default.
This will only show a stack trace for the line on which the warn method is called.
It is therefore recommended to use a stacklevel of 2 or greater
to provide more information to the user.

compute_endpoint/tests/unit/test_endpointmanager_unit.py:765:5:
B017 `assertRaises(Exception)` and `pytest.raises(Exception)` should be considered evil.
They can lead to your test passing even if the code being tested is never executed due to a typo.
Assert for a more specific exception (builtin or custom),
or use `assertRaisesRegex` (if using `assertRaises`),
or add the `match` keyword argument (if using `pytest.raises`),
or use the context manager form with a target.

...

Type of change

Choose which options apply, and delete the ones which do not apply.

• Code maintenance/cleanup

[khk-globus]

Awesome; this is really helpful. Doing pretty much exactly this has been on my local TODO list for awhile (so I'm literally going to go remove that line!), but the how-to is not immediately top-of-mind for me.

The failing smoke tests are, I think, a factor of permissions rather than anything fundamentally wrong. If something is actually awry and I'm just not seeing it, then we can fix it up later.

Thankee kindly!