fix(remote_services): immediate result codes were collapsed to UNKNOWN

[bartolije]

When _send_command got a terminal result with no status_id, it called RemoteServiceStatus(result_code) with a bare string ("PERFORMED", "ERROR", ...). The constructor then ran if "status" in response: on that string — a string-in-string check that is False for these codes — so state silently fell through to ExecutionState.UNKNOWN. Callers had no way to distinguish a successful remote action from a server timeout.

Two changes:

1. _send_command (remote_services.py:299): wrap the bare code in the same dict shape the polling endpoint returns so the constructor extracts it through the existing path:

   RemoteServiceStatus({"status": {"result": result_code}})
   

2. RemoteServiceStatus.__init__: guard with isinstance(response, dict) and tolerate result codes outside the ExecutionState enum (e.g. a future "REJECTED") with a try/except ValueError — falling back to UNKNOWN instead of crashing during construction.

Concrete repro (no test infra needed):

>>> from pyporscheconnectapi.remote_services import (
...     RemoteServiceStatus, ExecutionState,
... )
>>> # Before this patch: silent UNKNOWN.
>>> # After:
>>> s = RemoteServiceStatus({"status": {"result": "PERFORMED"}})
>>> s.state == ExecutionState.PERFORMED
True