FEAT: Add rpyc option in launch_mechanical

[dipinknair]

launch_mechanical now provides two rpc options such as grpc ( backend = 'mechanical') and rpyc( backend = 'python') . By default, it is grpc
It can be used as given below.

import ansys.mechanical.core as pymechanical

mechanical = pymechanical.launch_mechanical(backend="python")
print(mechanical)

with rpyc option mechanical exists when python code completes.
with cleanup_on_exit option disabled , user can still use another client to connect the mechanical which is alive.

import ansys.mechanical.core as pymechanical

mechanical = pymechanical.launch_mechanical(backend="python", cleanup_on_exit=False)

[codecov]

Codecov Report

Attention: Patch coverage is 31.25000% with 22 lines in your changes missing coverage. Please review.

Project coverage is 86.60%. Comparing base (dad2a2c) to head (1991d40).
Report is 2 commits behind head on main.

❌ Your patch check has failed because the patch coverage (31.25%) is below the target coverage (90.00%). You can increase the patch coverage or adjust the target coverage.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1101      +/-   ##
==========================================
+ Coverage   79.74%   86.60%   +6.85%     
==========================================
  Files          43       43              
  Lines        2854     2881      +27     
==========================================
+ Hits         2276     2495     +219     
+ Misses        578      386     -192     

[koubaa]

@dipinknair I prefer the option to be like this:

launch_mechanical(backend=python)
launch_mechanical(backend=mechanical)

That way rpyc and grpc are implementation details.

[koubaa]

If you could use this in the fixture, it might increase testing coverage