DALServiceError for cosmodc2: maxrec

[bsipocz]

Note: this is a different error than #194, and seems to be persistent. The last passing build for this job was 14July, I suspect some of the jobs were actually failing on other temporary issues.

astropy==8.0.1
pyvo==1.9.1

[1](https://github.com/Caltech-IPAC/irsa-tutorials/actions/runs/31735574795/job/94566260133#step:7:2742)

tutorials/simulated-data/cosmoDC2_TAP_access.md
  - ⛔ An exception occurred during code execution, halting further execution:

---------------------------------------------------------------------------
DALServiceError                           Traceback (most recent call last)
Cell In[6], line 1
----> 1 service.maxrec

File ~/work/irsa-tutorials/irsa-tutorials/.tox/py312-buildhtml/lib/python3.12/site-packages/pyvo/dal/tap.py:240, in TAPService.maxrec(self)
    238 except AttributeError:
    239     pass
--> 240 raise DALServiceError("Default limit not exposed by the service")

DALServiceError: Default limit not exposed by the service

py312-buildhtml: exit 1 (1244.68 seconds) /home/runner/work/irsa-tutorials/irsa-tutorials> bash -c 'jupyter-book build --execute --execute-parallel 1 --html --strict -d' pid=2467
  py312-buildhtml: FAIL code 1 (1334.52=setup[84.68]+cmd[0.31,0.00,0.03,0.03,0.00,0.00,0.00,0.01,0.56,0.00,0.00,0.02,0.00,0.00,4.17,1244.68] seconds)
  evaluation failed :( (1334.57 seconds)
Error: Process completed with exit code 1.

[bsipocz]

OK, so the job on the 28 of July was passing for cosmodc2, on the 31st it was failing with a DALQueryError: TransientFault: INTERNAL_SERVER_ERROR: Job ran but timed out., passing on the 7th, and we started to see this particular issue on the 11th.

[bsipocz]

I am asking around for this from the backend team and will investigate further based on their response.

[bsipocz]

OK, so the server side has changed and we don't specify outputLimit capability any more.

However it's optional in TAPRegExt, so we probably shouldn't choke on it with pyvo.

OTOH, the tutorial explicitly calls service.maxrec, so the error message is correct, the server is not specifying it. But given it's optional, I suppose a more correct behaviour would be to return a None.
That being said, maxrec is not exactly the same out outputlimit, so this may actually point to an actual bug in pyvo, too.

Either case, I suppose we could/should remove this line and the surrounding narrative from the tutorial for now, as we don't enforce this limit on the server side.