Meshing queries refactoring, improved error handling and doc updates

[hpohekar]

---------------------------------------------------------------

---------------------------------------------------------------

---------------------------------------------------------------

[seanpearsonuk]

@hpohekar this is an observation rather than a criticism. The summary of each of these "service" objects focuses on the implementation: "wrapper over ... gRPC" rather than telling the reader what the "service" can offer them. This is bewildering for te average reader. #1586

[hpohekar]

@hpohekar this is an observation rather than a criticism. The summary of each of these "service" objects focuses on the implementation: "wrapper over ... gRPC" rather than telling the reader what the "service" can offer them. This is bewildering for te average reader. #1586

Right.

[hpohekar]

@seanpearsonuk regarding following mesh utility function,

We have useful supporting function to guide user about allowed arguments to above function.

---------------------------------------

[seanpearsonuk]

@seanpearsonuk regarding following mesh utility function,

We have useful supporting function to guide user about allowed arguments to above function.

---------------------------------------

I believe that we should use enums for such things.

[hpohekar]

@seanpearsonuk

This PR is now ready and consistent with what we are offering in 23R2.

It contains all required meshing queries utility functions, tests and documentation.

We will implement new changes in next PR as per our latest discussion.

Thanks.

[seanpearsonuk]

streaming doc changes in follow-up