fix: better error handling for invalid messages

[cristipufu]

Pull Request Overview

This PR improves error handling in the session runtime, conditions tracer initialization, and updates the package version.

• Wraps message processing in _run_server with a try/except to log errors and return a JSONRPCError to the client.
• Logs the server’s stderr output when capturing runtime errors.
• Only initializes the OpenTelemetry tracer if a job_id is present in the context.
• Bumps the project version from 0.0.93 to 0.0.94.

[Copilot]

Pull Request Overview

This PR improves error handling in the session runtime, conditions tracer initialization, and updates the package version.

• Wraps message processing in _run_server with a try/except to log errors and return a JSONRPCError to the client.
• Logs the server’s stderr output when capturing runtime errors.
• Only initializes the OpenTelemetry tracer if a job_id is present in the context.
• Bumps the project version from 0.0.93 to 0.0.94.

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
src/uipath_mcp/_cli/_runtime/_session.py	Added exception handling around incoming messages and stderr logging.
src/uipath_mcp/_cli/_runtime/_runtime.py	Guarded tracer setup on presence of context.job_id.
pyproject.toml	Updated project version to 0.0.94.

Comments suppressed due to low confidence (1)

src/uipath_mcp/_cli/_runtime/_session.py:143

• The new error-handling path isn’t covered by existing tests. Please add unit tests or integration tests to verify that invalid messages trigger the JSONRPCError response and that logging behaves as expected.

                            except Exception as e: