feat(scenarios): add timeoutSeconds to scenarios and steps

- add timeoutSeconds field to scenario and step entities
- add timeoutSeconds to create/update DTOs for scenario and step
- enforce timeout via scheduler: abort run if step exceeds limit
- expose timeoutSeconds in MCP create/update scenario and step tools
- add client-side type, API, i18n, and form support for timeoutSeconds
- add integration tests for timeout persistence via REST and MCP

client/src/api/client.ts

@@ -193,7 +193,7 @@ export const scenarios = {
       body: JSON.stringify({ name, description, environmentId }),
     });
   },
-  update(id: string, patch: Partial<Pick<Scenario, 'name' | 'description' | 'environmentId'>>): Promise<Scenario> {
+  update(id: string, patch: Partial<Pick<Scenario, 'name' | 'description' | 'environmentId' | 'timeoutSeconds'>>): Promise<Scenario> {
     return request(`/scenarios/${id}`, {
       method: 'PATCH',
       body: JSON.stringify(patch),
@@ -254,7 +254,7 @@ export const runs = {
     orderDir: 'ASC' | 'DESC' = 'DESC',
   ): Promise<
     PaginatedResponse<
-      ScenarioRun & { stepRuns: ScenarioRunStep[]; scenario: { id: string; name: string } }
+      ScenarioRun & { scenario: { id: string; name: string } }
     >
   > {
     const q = new URLSearchParams({ page: String(page), limit: String(limit), orderBy, orderDir });
@@ -299,12 +299,14 @@ export const scenarioCredentials = {
 export interface CreateStepPayload {
   title?: string;
   execCode?: string;
+  timeoutSeconds?: number | null;
 }
 
 export interface UpdateStepPayload {
   title?: string;
   order?: number;
   execCode?: string;
+  timeoutSeconds?: number | null;
 }
 
 export const steps = {