feat: hatch build change

[kierandidi]

📋 PR Checklist

• This PR is tagged as a draft if it is still under development and not ready for review.

  This avoids auto-triggering the slower tests in the CI and needlessly wasting resources.

• I have ensured that all my commits follow angular commit message conventions.

  Format: <type>[optional scope]: <subject>
  Example: fix(af3): add missing crop transform to the af3 pipeline

  This affects semantic versioning as follows:

  • fix: patch version increment (0.0.1 → 0.0.2)
  • feat: minor version increment (0.0.1 → 0.1.0)
  • BREAKING CHANGE: major version increment (0.0.1 → 1.0.0)
  • All other types do not affect versioning

  The format ensures readable changelogs through auto-generation from commit messages.

• I have run make format on the codebase before submitting the PR (this autoformats the code and lints it).

• I have named the PR in angular PR message format as well (c.f. above), with a sensible tag line that summarizes all the changes in the PR.

  This is useful as the name of the PR is the default name of the commit that will be used if you merge with a squash & merge.
  Format: <type>[optional scope]: <subject>
  Example: fix(af3): add missing crop transform to the af3 pipeline

---

ℹ️ PR Description

What changes were made and why?

How were the changes tested?

Additional Notes

[github-actions]

🎉 This PR is included in version 2.1.0 🎉

The release is available on:

• v2.1.0
• GitHub release

Your semantic-release bot 📦🚀