Ensure that failures during pyright invocation are properly surfaced in verifytypes

[scbedd]

Working through a transcription failure.

[Copilot]

Pull request overview

This PR improves the robustness of the azpysdk verifytypes flow by ensuring pyright --verifytypes failures that don’t emit valid JSON are clearly logged and treated as a failure, rather than causing an unhandled JSON parsing exception.

Changes:

• Guard json.loads(e.output) in verifytypes to handle non-JSON/empty output and surface stdout/stderr in logs.
• Fix incorrect logger.error(..., e) usage during dev requirements installation so the exception is properly included in the log message.

Show a summary per file

File	Description
eng/tools/azure-sdk-tools/azpysdk/verifytypes.py	Adds error handling for invalid/missing JSON output from pyright --verifytypes on return code 1.
eng/tools/azure-sdk-tools/azpysdk/Check.py	Fixes exception logging for dev requirements installation failures.

Copilot's findings

• Files reviewed: 2/2 changed files
• Comments generated: 1

[Copilot]

In this exception handler, raise e will re-raise the exception with a new traceback and can hide where the CalledProcessError actually originated. Use a bare raise (and optionally logger.exception(...) if you want the traceback in logs) to preserve the original traceback/context.

Suggested change

	raise e
	raise