ENH: Bump to ITK v5.3rc04

[tbirdso]

Bump to most recent ITK version. May require bumping dependencies first.

[dzenanz]

I understand impatience, but I advise not to spend time trying to update CIs prematurely.

[tbirdso]

@dzenanz

I understand impatience, but I advise not to spend time trying to update CIs prematurely.

My apologies for not clearly stating the PR intention. @thewtex and I spoke after the hackathon today on next steps for external modules with v5.3rc04, my understanding of the current goal is to ensure that external modules build with the ITK v5.3rc04 wheels before C++ release notes are published.

My initial attempt to upgrade ITKVkFFTBackend failed, apparently due to a pathing issue. My first thought was to attempt a similar bump on another external module to check whether this is an issue with ITKPythonPackage or with the ITKVkFFTBackend module.

I now realize that ITKUltrasound is not the best module for comparison because it depends on several other external modules. I would like to focus efforts on bumping ITKSplitComponents to build and package with v5.3rc04 wheels because its build structure is much less complicated.

Roadmap:

• Investigate Python CI failures in ITKSplitComponents with v5.3rc04
• Possibly make changes to ITKPythonPackage / rebuild wheels if necessary
• Bump ITKSplitComponents and other external modules (ITKVkFFTBackend, maybe ITKUltrasound and its remaining dependencies)
• Publish release notes for ITK v5.3rc04

[thewtex]

To simplify version configuration and make it easier to use other remote modules, in the process of makes these updates to ITKUltrasound, related modules, we should adopt the approach @aylward has taken in ITKTubeTK's configuration in these modules, then add that to the ITKModuleTemplate.

[tbirdso]

ITK v5.3rc04 build archives are now stable (see https://github.com/insightsoftwareconsortium/itksplitcomponents for example of successful v5.3rc04 package). Pushing this forward as a prerequisite for #182.

[tbirdso]

Note linter failures are tracked in InsightSoftwareConsortium/ITKSplitComponents#52 and result from a recent git security patch. A fix appears to be forthcoming from Github Actions. For now linter failures should not be considered blocking.

[tbirdso]

@dzenanz @thewtex Ping for review

[tbirdso]

Note linter issue has been resolved by Github Actions