Use pyproject.toml to specify build requirements

[ksivaman]

Description

setup_requires is deprecated (pep ref) and will be removed in setuptools v75.0.0. This PR uses the newer pyproject.toml to specify build time dependencies. We can consider gradually moving over other functionality to pyproject.toml as required.

Type of change

• Documentation change (change only to the documentation, either a fix or a new content)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Infra/Build change
• Code refractor

Changes

Please list the changes introduced in this PR:

• Change A
• Change B

Checklist:

• I have read and followed the contributing guidelines
• The functionality is complete
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[ksivaman]

/te-ci

[timmoon10]

Modernizing to use pyproject.toml would be nice for multiple reasons, but it will probably break user workflows (see #981 (comment)). In particular, pip install . will no longer work and users will need to add the ---no-build-isolation flag. It may be worthwhile, but we should be aware.

[timmoon10]

check_call is nice since it will print out the error message if the process fails:

Suggested change

	subprocess.run(
	subprocess.check_call(

We could alternatively call with check=True or manually check the return code.

[yaox12]

Can we add a section for the black formatter in pyproject.toml to declare the following arguments? It's useful when we want to format the code locally.

TransformerEngine/.pre-commit-config.yaml

Line 31 in a326e35

args: [--line-length=100, --preview, --enable-unstable-feature=string_processing]