Use an older version of setuptools when installing requirements

[seanbudd]

Link to issue number:

None

Summary of the issue:

setuptools has been updated, breaking support with py2exe: py2exe/py2exe#208.

When installing packages, pip automatically pulls in the latest build dependences as specified in PEP 518.
pip creates a custom temporary build environment to install packages using the latest pip environment.

Description of development approach

Create a pyproject.toml to specify the build environment we are using.
https://packaging.python.org/en/latest/guides/writing-pyproject-toml/

Use the flag no-build-isolation when installing requirements.txt.
This prevent pip from using the custom build environment and automatically pulling the latest setuptools when installing packages.

As such, we need to manually install the desired version of setuptools, and manually install pip's dependency wheel.
https://stackoverflow.com/questions/62889093/what-does-no-build-isolation-do

Testing strategy:

Ensure build completes successfully

Known issues with pull request:

None

Code Review Checklist:

• Documentation:
  • Change log entry
  • User Documentation
  • Developer / Technical Documentation
  • Context sensitive help for GUI changes
• Testing:
  • Unit tests
  • System (end to end) tests
  • Manual testing
• UX of all users considered:
  • Speech
  • Braille
  • Low Vision
  • Different web browsers
  • Localization in other languages / culture than English
• API is compatible with existing add-ons.
• Security precautions taken.

[AppVeyorBot]

• Build execution time has reached the maximum allowed time for your plan (60 minutes).

See test results for failed build of commit 2b613c8d37

[CyrilleB79]

Isn't there any impact for local builds?

[AppVeyorBot]

• Build execution time has reached the maximum allowed time for your plan (60 minutes).

See test results for failed build of commit d5f845a906

[seanbudd]

@CyrilleB79 - yes there may be, the current approach should fix this for local environments. I haven't been able to reproduce this locally so I cannot confirm.

[seanbudd]

@dpy013 - we will likely have to migrate from py2exe due to no python 3.12 support.
This is out of scope of this PR, we need to fix the build system immediately and this is a large project.

py2exe/py2exe#191