connect_to_mechanical() tries to run/create "mylocal.ip" file in customer environment leading to error

### Before submitting the issue

- [x] I have verified whether the issue reproduces in Mechanical directly (paste your script into the Mechanical scripting window or run it in batch mode via `ansys-mechanical -i test.py`). If it reproduces there, the issue is likely in Mechanical rather than PyMechanical.
If it is an issue in Mechanical, please check with the Ansys support coordinator (ASC) at your company to determine who provides support for your company, or submit a request via the [Ansys Customer Support portal](https://www.ansys.com/support).
- [x] I have searched among the existing issues
- [x] I am using a Python virtual environment

### Description of the bug

connect_to_mechanical() tries to run/create "mylocal.ip" file in customer environment leading to error

### Steps To Reproduce

It's in customer environment, not reproducible in internal environment

### Which Operating System are you using?

Windows

### Which Python version are you using?

3.12

### Which Ansys Mechanical version are you using?

2025 R2 (252)

### Installed packages

''

The reported entry point is connect_to_mechanical(); begin by tracing its behavior in the Windows, Python 3.12, Mechanical 2025 R2 customer setup and determine why mylocal.ip is run or created. Done means the connection no longer attempts that customer-environment file operation and the fix is verified against the reported scenario.

Written by the indexing model from the issue text.