Apply pyupgrade fixes missing from ruff

[maresb]

Description

In the course of #586 we observed that newer versions of pyupgrade (the current latest 3.15.0 vs the outdated 3.3.1 configured in .pre-commit-config.yaml) caught a few more issues that ruff missed. I'm not sure why; perhaps pyupgrade is more up-to-date than ruff.

We can merge these particular fixes, but it's probably worth considering what to do here in general. Like should we still run pyupgrade, and perhaps also flake8 in the CI to ensure that ruff isn't missing stuff?

Related Issue

• Closes #
• Related to #

Checklist

• Checked that the pre-commit linting/style checks pass
• Included tests that prove the fix is effective or that the new feature works
• Added necessary documentation (docstrings and/or example notebooks)
• If you are a pro: each commit corresponds to a relevant logical change

Type of change

• New feature / enhancement
• Bug fix
• Documentation
• Maintenance
• Other (please specify):

[maresb]

Not sure why coverage is failing, but it looks like a remote failure instead of something from our side.

[ricardoV94]

Not sure why coverage is failing, but it looks like a remote failure instead of something from our side.

Yeah, let's keep an eye in the near term