feat: adding more descriptive errors

[germa89]

Description

More descriptive gRPC errors.

Issue linked

Close #2844
Close #3318

Checklist

• I have visited and read Develop PyMAPDL.
• I have tested my changes locally
• I have added necessary documentation or updated existing documentation.
• I have followed the PyMAPDL coding style guidelines.
• I have added appropriate unit tests that also ensure the minimal coverage criteria.
• I have reviewed my changes before submitting this pull request.
• I have linked the issue or issues that are solved to the PR if any.
• I have assigned this PR to myself.
• I have marked this PR as draft if it is not ready to be reviewed yet.
• I have made sure that the title of my PR follows Commit naming conventions (e.g. feat: adding new MAPDL command)

[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

Attention: Patch coverage is 70.27027% with 11 lines in your changes missing coverage. Please review.

Project coverage is 87.10%. Comparing base (a8b1514) to head (acf39fd).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3319      +/-   ##
==========================================
- Coverage   87.13%   87.10%   -0.03%     
==========================================
  Files          55       55              
  Lines        9773     9790      +17     
==========================================
+ Hits         8516     8528      +12     
- Misses       1257     1262       +5     

[germa89]

We won't care about coverage for this one.

[germa89]

Pinging @clatapie for review

[germa89]

traceback now looks:

Error:
MAPDL server connection terminated unexpectedly while running:
  SOLVE,
called by:
  _send_command_stream

Error:
  Socket closed
Full error:
<_MultiThreadedRendezvous of RPC that terminated with:
        status = StatusCode.UNAVAILABLE
        details = "Socket closed"
        debug_error_string = "UNKNOWN:Error received from peer ipv4:127.0.0.1:50062 {grpc_message:"Socket closed", grpc_status:14, created_time:"2024-08-08T19:09:47.964845+02:00"}"
>
Solve seems to have failed, retrieving .err files.
Traceback (most recent call last):
  File "/Users/german.ayuso/pymapdl/src/ansys/mapdl/core/errors.py", line 310, in wrapper
    out = func(*args, **kwargs)
  File "/Users/german.ayuso/pymapdl/src/ansys/mapdl/core/mapdl_grpc.py", line 2041, in _get
    getresponse = self._stub.Get(pb_types.GetRequest(getcmd=cmd))
  File "/Users/german.ayuso/pymapdl/.venv/lib/python3.10/site-packages/grpc/_channel.py", line 1176, in __call__
    return _end_unary_response_blocking(state, call, False, None)
  File "/Users/german.ayuso/pymapdl/.venv/lib/python3.10/site-packages/grpc/_channel.py", line 1005, in _end_unary_response_blocking
    raise _InactiveRpcError(state)  # pytype: disable=not-instantiable
grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with:
        status = StatusCode.UNAVAILABLE
        details = "failed to connect to all addresses; last error: UNAVAILABLE: ipv4:127.0.0.1:50062: recvmsg:Connection reset by peer"
        debug_error_string = "UNKNOWN:Error received from peer  {grpc_message:"failed to connect to all addresses; last error: UNAVAILABLE: ipv4:127.0.0.1:50062: recvmsg:Connection reset by peer", grpc_status:14, created_time:"2024-08-08T19:09:48.15481+02:00"}"

[germa89]

Again...

We won't care about coverage for this one.

I need this PR so...

@pyansys-ci-bot LGTM.

[pyansys-ci-bot]

✅ Approving this PR because germa89 said so in here 😬