ENH: customising reps for nonTable classes

[bsipocz]

This is a draft for solutions for #476

If you all like this approach, I would do this systematically for all the __repr__s we have elsewhere in the library.

See the equivalent for VOTable in astropy: astropy/astropy#14702

[codecov]

Codecov Report

Merging #478 (6094999) into main (2092174) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #478   +/-   ##
=======================================
  Coverage   80.00%   80.00%           
=======================================
  Files          52       52           
  Lines        6035     6035           
=======================================
  Hits         4828     4828           
  Misses       1207     1207           

Files Changed	Coverage Δ
pyvo/dal/query.py	84.81% <100.00%> (ø)

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[tomdonaldson]

I like the simplicity of this approach and the output is much improved. I think it makes sense to systematically apply across the board. That doesn't preclude us from future customizations of certain __repr__ s if the type would benefit from additional or different information.

[bsipocz]

OK, actually I think this is the only instance of the confusing repr, everywhere else it already reflects the classname or at least the name of one of its base classes.

The one more improvement we may consider is subclasses of DALResults all say a DALResultsTable in their __repr__, ultimately we may want to distinguish between them?