fix: avoid verbose grpc interface when solving

[germa89]

Description

This PR solves #3591 issue. This issue covers the instability/bug seen where MAPDL gets stuck while running some commands, very frequently, the /SOLVE command.

The reason for this is that some MAPDL printouts was making MAPDL to wait infinitely for the next line.
These specific prints in MAPDL terminal were coming from a debug messenger (_MsgDbg1), an object which prints more output (sometimes for debugging purposes) if it is activated.
It seems this debug messenger is activated by default, but deactivated if we issue /VERIFY.
Additionally, the debugger can be also activated if we activate the gRPC debug messenger (mapdl._ctrl("set_verb", 5)) since these kind of messengers are singleton objects (unique in the whole program).

MAPDL was getting stuck because for reading the anstmp file, it uses std:getline (only!), hence if the line is empty, the getline waits forever. See https://stackoverflow.com/a/39905660/6650211

Until now, we did not realise because the first test running solve:

pymapdl/tests/test_commands.py

Lines 252 to 265 in afad43e

	def test_bclist(mapdl, beam_solve, func):
	func_ = getattr(mapdl, func)
	out = func_()
	out_list = out.to_list()
	assert isinstance(out, BoundaryConditionsListingOutput)
	assert isinstance(out_list, list) and out_list
	with pytest.raises(ValueError):
	out.to_array()
	if has_dependency("pandas"):
	out_df = out.to_dataframe()
	assert isinstance(out_df, pd.DataFrame) and not out_df.empty

was using this fixture:

pymapdl/tests/test_commands.py

Lines 147 to 153 in afad43e

	def beam_solve(mapdl, cleared):
	mapdl.mute = True
	mapdl.input(vmfiles["vm10"])
	mapdl.post1()
	mapdl.set(1, 2)
	mapdl.mute = False

Which a verification manual example, which uses /VERIFY.
The command /VERIFY avoid printing these extra debug printouts.

Clearly this is a server side bug which should be fixed in the future versions. But for the moment, I am going to force MAPDL to run /VERIFY when we instantiate the object.

Issue linked

Related to #3591

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

All modified and coverable lines are covered by tests ✅

Project coverage is 86.99%. Comparing base (afad43e) to head (1d63ba0).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3608      +/-   ##
==========================================
+ Coverage   86.97%   86.99%   +0.01%     
==========================================
  Files         187      187              
  Lines       14623    14628       +5     
==========================================
+ Hits        12719    12725       +6     
+ Misses       1904     1903       -1     

[germa89]

@pyansys-ci-bot LGTM.

[pyansys-ci-bot]

✅ Approving this PR because germa89 said so in here 😬