FEAT: Install pyaedt via uv

[eblanco-ansys]

Description

Use uv to install pyaedt dependencies. Implemented changes

• Virtual environments are still created with python -m venv until Package seems not to work pymechanical#1143 and the associated uv issue Windows: OpenSSL installed DLL name differs from CPython, affecting extension modules astral-sh/python-build-standalone#596 are resolved
• For online installation, uv is installed firstly and the other packages are installed via uv pip install (a lot faster)
• For wheel installation with no internet, uv is intalled firstly. We then use uv to install the other packages inside the wheel.
  With these changes we reduce a lot the overall installation time, up to 5 times.

Other minor changes:

• Unzip function now supports recursivity. For dev wheelhouses, when the file is unzipped there is another zip inside the unzipped folder. This should be solved in the github action, this is a workaround.
• Files are unzipped in a temporal directory

Issue linked

#6317

Checklist

• I have tested my changes locally.
• I have added necessary documentation or updated existing documentation.
• I have followed the coding style guidelines of this project.
• I have added appropriate tests (unit, integration, system).
• I have reviewed my changes before submitting this pull request.
• I have linked the issue or issues that are solved by the PR if any.
• I have agreed with the Contributor License Agreement (CLA).

[ansys-reviewer-bot]

Thanks for opening a Pull Request. If you want to perform a review write a comment saying:

@ansys-reviewer-bot review

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.44%. Comparing base (003149d) to head (d01cc8e).
⚠️ Report is 5 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #6338   +/-   ##
=======================================
  Coverage   82.44%   82.44%           
=======================================
  Files         242      242           
  Lines       77004    77004           
=======================================
  Hits        63485    63485           
  Misses      13519    13519           

🚀 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.

[SMoraisAnsys]

Could you give a try at making the whole project moving to uv instead of only this installation file ? Also, could you consider using UV_HTTP_TIMEOUT in order to keep the previous behavior with ``--default-timeout` ? It has a larger scope but if I understand well the documentation it should be helping for this.

[SMoraisAnsys]

Here are some comments, thanks for the contribution !
Note that we might have issues when using pyaedt with uv. In particular for those still leveraging the dotnet target.
See ansys/pymechanical#1143 and the associated uv issue astral-sh/python-build-standalone#596

[eblanco-ansys]

Should we merge this PR? PyAEDT issues using uv can be avoided creating the venv in the traditional way and installing packages via uv. With the actual implementation should work fine

[Samuelopez-ansys]

@eblanco-ansys The main issue is about the offline installation. Is this solved?

If uv is not installed in the venv , how the offline installation would work? We could add uv to the dependencies of pyaedt or at least to the wheelhouses

@SMoraisAnsys any thoughts?

[SMoraisAnsys]

@eblanco-ansys The main issue is about the offline installation. Is this solved?

If uv is not installed in the venv , how the offline installation would work? We could add uv to the dependencies of pyaedt or at least to the wheelhouses

@SMoraisAnsys any thoughts?

Adding uv to the all target wheelhouse would be a solution considering the current approach and how to address offline installation. Are all the previously mentioned concerns addressed ?

[eblanco-ansys]

@eblanco-ansys The main issue is about the offline installation. Is this solved?
If uv is not installed in the venv , how the offline installation would work? We could add uv to the dependencies of pyaedt or at least to the wheelhouses
@SMoraisAnsys any thoughts?

Adding uv to the all target wheelhouse would be a solution considering the current approach and how to address offline installation. Are all the previously mentioned concerns addressed ?

All the previous concerns were related to how the venv is created. If we create the venv in the traditional way and install everything via uv, it should be fine. @tusharbana-ansys figured out this workaround