Databricks registration blocks loading of other spicepods

[digadeesh]

To Reproduce
Set up a databricks dataset, and a separate dataset (in this case I used S3 quickstart).
Stop your databricks compute and start the spice runtime. You'll see:
2024-05-21T23:22:11.922975Z INFO spiced: Metrics listening on 127.0.0.1:9000
2024-05-21T23:23:12.240350Z WARN runtime: Unable to get read provider for databricks: Io error: status: Internal, message: "protocol error: received message with invalid compression flag: 60 (valid flags are 0 and 1) while receiving response with status: 504 Gateway Timeout", details: [], metadata: MetadataMap { headers: {} }
2024-05-21T23:23:27.603261Z WARN runtime: Unable to get read provider for databricks: Analysis error: TEMPORARILY_UNAVAILABLE: Waiting for the cluster to become available. This is expected for new sessions. Please try again. [state=PENDING] (requestId=c31ea701-6723-4ed6-9783-bff0256120c9)

Use the spice repl and do a show tables:

observe that failing to load one dataset blocks loading of all others until the issue is resolved.

Expected behavior
The other datasets can load while the databricks (or other datasets) can load.

Additional context
Add any other context about the problem here.

[digadeesh]

Fixed in #1551