Accept a Python range when setting scoping IDs.

[PProfizi]

Hi @JennaPaikowsky, the PR for the field inspired me to do this for the Scoping class as I noticed we were doing list(range(*)) in the docstring examples for the Field when defining a Scoping.

This PR mainly adds the support for a range as input when setting the IDs of a scoping.

It also adds type hinting and improves the docstrings a bit. I'll also add some docstring examples and testing.

I'll actually add the AnyServerType type for type hint in a dedicated PR if @moe-ad and @jorgepiloto confirm this is the correct way to provide a combination of allowed types for type hints in the rest of the library. See #2002

@jorgepiloto @moe-ad one thing I would like our opinion on is the type hint for pointers and Grpc messages as I think it will not work as-is. Edit: it looks like it does! Even though the IDE is complaining that ansys.grpc.dpf.scoping_pb2.Scoping does not exist.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.38%. Comparing base (52ed660) to head (72b1a43).
Report is 4 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #2001      +/-   ##
==========================================
- Coverage   88.40%   88.38%   -0.02%     
==========================================
  Files          89       89              
  Lines       10252    10261       +9     
==========================================
+ Hits         9063     9069       +6     
- Misses       1189     1192       +3     

[rafacanton]

@PProfizi I see post ci failing, do we need a PR there to support something related to the server? Otherwise, this LGTM!

[PProfizi]

Ah, indeed, @rafacanton the scoping factory for named selections has a server parameter which is not used. I removed it but of course this is not backwards compatible with existing calls.

[JennaPaikowsky]

A couple of minor points.