use ansys-tool-path, instead of using the env variable

[kmahajan-cadfem]

updated the installer code, so that it uses ansys-tools-pathlibrary to deduce the versions that are installed, and then checks for the python that is available.

PS: I was not able to make the builds with following

on windows

• make build
• and then compile setup.nsis with NSIS local installaion

[RobPasMue]

Hi @kmahajan-cadfem! Sounds great, thanks for opening this PR. Let me try the commands locally.

[RobPasMue]

FYI @kmahajan-cadfem - see my video. Managed to run make build successfully on a clean env

video.webm

[RobPasMue]

LGTM! Merging!

[kmahajan-cadfem]

@RobPasMue,

Thank you for the video, I did not write initial comment correctly.
sorry for confusion.

I was able to build it 👍 and also compile it, unfortunately could not run either the built exe or even the installed exe (after compiling, did the installation)

I think there maybe a step in Github actions that I did not follow, but that is fine, I wanted to make sure that it would work after installation as well.

[RobPasMue]

Due to your active contributions @kmahajan-cadfem we have sent you an invitation as an outside collaborator. Feel free to accept or reject it. We want to thank you all your support! I will also add you to the contributors list if you agree. I will do that on a follow-up PR (before doing a new release).