[coverage] Conformance findings: ERRORRECOV-013,ERRORRECOV-014

[peco-engineer-bot]

Surfaced by the multi-language coverage fan-out while conformance-testing these SPEC-IDs against databricks/databricks-sql-nodejs.

Each is committed as an expected-failure (xfail) test in the coverage PR — the test asserts the CORRECT behavior and stays red until this driver is fixed.

• ERRORRECOV-013: Terminal CloudFetch chunk-download failure surfaces "Error: Max retry count exceeded" — no download/cloudfetch/chunk/cloud-storage attribution, so telemetry falls back to the generic error category (PECOBLR-3537)
• ERRORRECOV-013: Terminal CloudFetch chunk-download failure surfaces "Error: Internal: HTTP 500: Internal Server Error" from the kernel — no download/cloudfetch/chunk/cloud-storage attribution, so telemetry falls back to the generic error category (PECOBLR-3537)
• ERRORRECOV-014: Terminal FetchResults failure surfaces the raw "THTTPException: Received a response with a bad HTTP status code: 500" with no result-retrieval attribution and no reachable cause chain (cause/underlying/innerError absent), losing the originating transport failure (PECOBLR-3537)

Reference driver PR: databricks/databricks-sql-go#417
Coverage PR (reproducing xfail tests): https://github.com/databricks/databricks-driver-test/pull/991