catch json error

[danmoseley]

Description

Fix #9368

Philosophically perhaps this should go in the dotnet CLI which shouldn't dump this stack.

Fixes # (issue)

Checklist

• Is this feature complete?
  • Yes. Ready to ship.
  • No. Follow-up changes expected.
• Are you including unit tests for the changes and scenario tests if relevant?
  • Yes
  • No
• Did you add public API?
  • [] Yes
    • If yes, did you have an API Review for it?
      • Yes
      • No
    • Did you add <remarks /> and <code /> elements on your triple slash comments?
      • Yes
      • No
  • No
• Does the change make any security assumptions or guarantees?
  • Yes
    • If yes, have you done a threat model and had a security review?
      • Yes
      • No
  • No
• Does the change require an update in our Aspire docs?
  • Yes
    • Link to aspire-docs issue (consider using one of the following templates):
      • New (or update) doc-idea template
      • New breaking-change template
      • New diagnostic template
  • No

[Copilot]

Pull Request Overview

This PR addresses #9368 by improving error handling for JSON parsing in the DotNetCliRunner. Key changes include wrapping the JSON parse call in a try...catch block, logging a clear error message when parsing fails, and returning an appropriate error code.

[Copilot]

Pull Request Overview

This PR addresses issue #9368 by adding error handling around JSON parsing of package search results to prevent stack traces from being dumped.

• Wraps JSON parsing logic in a try-catch block
• Logs a concise error message and returns a specific exit code on JSON errors