Transition remote modules configuration from `setup.py` to the modern `pyproject.toml` about itk HOT 4 OPEN

Re #4748 (comment)

I am not bumping to newer ITK versions when transitioning to pyproject.toml: I am leaving unmodified the ITK dependency version that is transferred automatically from setup.py to pyproject.toml. Do you want me to require "itk>=5.4" for all of them while adopting pyproject.toml?

In the process of updating these, we could consider also changing the default branch from master to main,

Can do that right after the PRs are merged.

from itk.

@jhlegarreta thank you for your help with this! 💯 🥇

I did not bump the versions for the remotes while opening the PRs. @thewtex let me know your thoughts. Major, minor, patch, none?

I think we should bump the major version. Experience has shown that the packages are not binary compatible across itk major or minor releases. Following semantic versioning, this is a major bump.

In the process of updating these, we could consider also changing the default branch from master to main,

from itk.

I am not bumping to newer ITK versions when transitioning to pyproject.toml: I am leaving unmodified the ITK dependency version that is transferred automatically from setup.py to pyproject.toml. Do you want me to require "itk>=5.4" for all of them while adopting pyproject.toml?

Yes, please. itk == 5.4.* to be specific (or itk-core == 5.4.* if it only requires itk-core, etc.) We should update the script to do so automatically, too.

from itk.

Yes, please. itk == 5.4.* to be specific (or itk-core == 5.4.* if it only requires itk-core, etc.) We should update the script to do so automatically, too.

OK, done. The script does update to itk == 5.4.* in most cases (e.g. it does not when no specific version of itk has been specified, for example).

Edit: leaving bumping version of ITKTubeTK to @aylward.

from itk.