Pulumi: Migrate pyproject to PyPA standard and hatch

[JimMadge]

✅ Checklist

• You have given your pull request a meaningful title (e.g. Enable foobar integration rather than 515 foobar).
• You are targeting the appropriate branch. If you're not certain which one this is, it should be develop.
• Your branch is up-to-date with the target branch (it probably was when you started, but it may have changed since then).
• You have marked this pull request as a draft and added '[WIP]' to the title if needed (if you're not yet ready to merge).
• You have formatted your code using appropriate automated tools (for example ./tests/AutoFormat_Powershell.ps1 -TargetPath <path to file or directory> for Powershell).

⤴️ Summary

Migrate to hatch/hatchling.

• Use hatchling for build backend
• Use hatch for development
• Use standards PEP508, PEP440, PEP621
• Demonstrate using hatch environments for, linting, testing, building, etc.

🌂 Related issues

Check #1510 before merging

🔬 Tests

[JimMadge]

@jemrobinson This is not ready for review yet but would like your thoughts.

Especially on how to merge this (if we want to) without disrupting other work on the pulumi branch.

[jemrobinson]

Mostly happy but a few questions on details. Also, we should check for compatibility with #1509 which adds some dependencies.

[JimMadge]

Mostly happy but a few questions on details. Also, we should check for compatibility with #1509 which adds some dependencies.

👍 Can we agree to hold work on the python-migration branch after #1509 merges to let me get linting passing on this branch and merge it?

[jemrobinson]

I think this and #1509 can be merged in either order. Just need to be aware that they are inter-dependent.

[JimMadge]

No, because I'll need to fix all the black and ruff errors to not break CI in main. That will involve touching (potentially) every Python file in the repo.

That's why I want other work on this branch to stop before I start fixing the linting errors. Resolving merge conflicts will be too difficult otherwise.

[jemrobinson]

Typer requires Optional[type] rather than type | None. Otherwise you get the message:

RuntimeError: Type not yet supported: str | None

[jemrobinson]

Tested by redeploying an SHM and SRE.