Use logging library for status updates

[gordonwatts]

This PR will exchange some of the rich.print calls that happen as the library runs and route them through logging.info and logging.warning and logging.error.

• Less inline output while library is running
• Allows user of library to control how much output is printed
• Brings it into line for the "correct" way to use library, according to python.

[codecov]

Codecov Report

Attention: Patch coverage is 72.41379% with 8 lines in your changes are missing coverage. Please review.

Project coverage is 74.97%. Comparing base (5bc25f1) to head (b0d1b00).
Report is 4 commits behind head on 3.0_develop.

Files	Patch %	Lines
servicex/query.py	82.60%	4 Missing ⚠️
servicex/servicex_client.py	33.33%	4 Missing ⚠️

Additional details and impacted files

@@               Coverage Diff               @@
##           3.0_develop     #371      +/-   ##
===============================================
+ Coverage        73.78%   74.97%   +1.19%     
===============================================
  Files               42       42              
  Lines             2300     2406     +106     
===============================================
+ Hits              1697     1804     +107     
+ Misses             603      602       -1     

Flag	Coverage Δ
unittests	74.97% <72.41%> (+1.19%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[gordonwatts]

There is a chance that some of these logging.info should be downgraded to logging.debug.

[BenGalewsky]

Formatting changes in the same commit as the code changes make the review a lot harder. If you want to change formatting, it's more polite to make that a single commit and then have the meat of the PR in a second commit

[BenGalewsky]

Could you make the logger class variables in these two classes? It seems messy to keep repeating the logging.get_logger("__name__")