fix(datastore): Log when a DDS fails to load, including dataStore metadata

[markfields]

Description

When a DDS fails to load, we need to know what DataStore it was under for diagnostic purposes. But in some cases (e.g. if it's the Summarizer client), the stack that first awaits the getChannel call doesn't afford any insight into which DataStore it was, and we just get the raw error at a higher level choke point (e.g. Summarizer failing and closing), with no helpful context besides what we can glean from the minified stack.

This PR adds a catch-log-throw block around the internal channelP promise so as soon as it rejects, we get a log that includes DataStore metadata (its ID and package path).

[github-actions]

Hi! Thank you for opening this PR. Want me to review it?

Based on the diff (287 lines, 6 files), I've queued these reviewers:

• Correctness — logic errors, race conditions, lifecycle issues
• Security — vulnerabilities, secret exposure, injection
• API Compatibility — breaking changes, release tags, type design
• Performance — algorithmic regressions, memory leaks
• Testing — coverage gaps, hollow tests

How this works

• Adjust the reviewer set by ticking/unticking boxes above. Reviewer toggles alone don't trigger anything.

• Tick Start review below to dispatch the review fleet.

• After review finishes, tick Start review again to request another run — it auto-resets after each dispatch.

• This comment updates as new commits land; your reviewer selections are preserved.

• Start review

[markfields]

Tagging as release-blocking, this is blocking the safe rollout of a feature in a 1P partner

[Copilot]

Copilot reviewed 6 out of 6 changed files in this pull request and generated no comments.