Error Logging Enhancement Remote PyMechanical

### 📝 Description of the feature

Assuming there is an issue with the Mechanical script being passed on to the remote instance, the returned error message has only partial hints on what went wrong. The returned string is a raw text; hints are hidden in a block with other GRPC related errors.

For instance, line number is not mentioned in the error message below, where intentionally a syntax mistake was made. This is well handled with embedded PyMechanical instance, if it is possible to enhance the error logging for remote instance analogous to embedded instance with proper formatting and line number that would significantly improve the debugging efforts.

### 💡 Steps for implementing the feature

_No response_

### 🔗 Useful links and references

_No response_

Start by tracing how a script sent to the remote Mechanical instance is executed and how its raw gRPC error string is returned, then compare that behavior with the embedded PyMechanical instance. Done means remote syntax errors are formatted like embedded-instance errors and include the relevant line number without obscuring details among gRPC errors.

Written by the indexing model from the issue text.