chore: update build system requirements in pyproject.toml

[navinkarkera]

We are using the PEP 639 license syntax

license = "MIT"
license-files = ["LICENSE"]

This requires setuptools 77 or newer. Without an explicit [build-system], isolated builds may use an older setuptools version and fail while validating project.license.

It is currently failing while migrating wgu-ulmo instance to launchpad.

• Setuptools PEP 639 migration guide: https://setuptools.pypa.io/en/stable/userguide/license_migration.html

But turns out that Open edX Ulmo currently constrains setuptools to 69.1.1, so we cannot use the new syntax.

Merge checklist:
Check off if complete or not applicable:

• Version bumped
• Changelog record added
• Documentation updated (not only docstrings)
• Fixup commits are squashed away
• Unit tests added/updated
• Manual testing instructions provided
• Noted any: Concerns, dependencies, migration issues, deadlines, tickets

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 91.50%. Comparing base (02c6739) to head (7c2bcd0).
⚠️ Report is 10 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master      #13      +/-   ##
==========================================
+ Coverage   89.27%   91.50%   +2.22%     
==========================================
  Files          10       10              
  Lines         289      400     +111     
  Branches       21       35      +14     
==========================================
+ Hits          258      366     +108     
- Misses         27       30       +3     
  Partials        4        4              

Flag	Coverage Δ
frontend	91.48% <ø> (-0.42%)	⬇️
python	91.54% <ø> (+17.73%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.