Apply pyupgrade fixes for Python 3.9+ syntax

[jamesobutler]

Description

Included is a commit here applying pyupgrade changes for Python 3.8+ syntax. This should have been included in 104a360 when Python 3.7 support was dropped.

Also included is a commit here apply pyupgrade changes for Python 3.9+ syntax. This should have been included in 14b086b when Python 3.8 support was dropped.

I've also run the pre-commit autoupdate command to use the latest versions of the various pre-commit hook repos. It appears that pre-commit.ci bot has not been doing this on the quarterly schedule as expected? It appears the last time it submitted the PR to update the pre-commit hook repos was back in #6286 from April 2023.

Types of changes

• Non-breaking change (fix or new feature that would not break existing functionality).

[KumoLiu]

Hi @jamesobutler, thanks for the PR.
Could you please help take a look at the ci error: https://github.com/Project-MONAI/MONAI/actions/runs/11355141675/job/31583909844?pr=8150#step:8:13833

[ericspod]

It looks good to me, the errors popping up are a little weird and maybe something incompatible buried in Pytorch.

[jamesobutler]

I've attempted to avoid the typing related changes, but yeah I'm not sure what is going here with the code not being able to handle the post-upgrade. premerge-min / min-dep-pytorch (latest) check is successful, but the older pytorch status checks are not.

[jamesobutler]

I have rebased this branch against latest dev so that mass bulk changes would apply to latest code.

I don't generally like large file exclusions, but I've excluded some files from the pyupgrade pre-commit action and as a result monai tests have begun to pass again. This PR now represents an improvement and removal of the pyupgrade exceptions can come in the future along with more debugging. Maybe the issue will resolve itself upon dropping support for Python 3.9 and the typing support that was available in that version.

[KumoLiu]

/build

[jamesobutler]

@KumoLiu Should the GPU-quick-py3 still be a required status check for the protected dev branch or should it be removed? It appears it was set to not run as of 18a671a which was well over a year ago. It is listed as a required status check, but it has been constantly been getting skipped (https://github.com/Project-MONAI/MONAI/actions/workflows/pythonapp-gpu.yml). It seems like the pythonapp-gpu.yml could be removed from the source repository so that it no longer runs or at least modified to not run on pull request opened.

https://github.com/Project-MONAI/MONAI/actions/runs/11500638643/workflow?pr=8150

[KumoLiu]

@KumoLiu Should the GPU-quick-py3 still be a required status check for the protected dev branch or should it be removed?

Hi @jamesobutler, yes it's required and the workflow has been move to the blossom, so it is run in this pipeline: https://github.com/Project-MONAI/MONAI/actions/runs/11502209707.

[jamesobutler]

@KumoLiu I see that blossom-ci is a required status check, but it doesn't seem like GPU-quick-py3 should be set as a required status check for a PR. Enforcing all status checks to pass prior to integrating into a protected branch would require it to be constantly overruled by an admin enforcement since the rule isn't being respected.

[KumoLiu]

@jamesobutler, Thanks for pointing out, I just updated that part, seems it's out of the date.