Cannot navigate directly to a queued job from Quick execute

[zvonimirfras]

Problem

After a user queues a conversation from Quick execute, the success notification includes the newly created job ID. The available action can only navigate to the general Jobs page; there is no way to open or focus the specific job that was just created.

This makes it difficult to monitor the queued/running job, especially when the Jobs page contains many records or the new job is not visible on the current page.

Current behavior

1. Open Quick execute.
2. Select an agent and conversation.
3. Select Execute conversation.
4. A success notification confirms the job was queued and displays its ID.
5. Select View jobs.
6. The general Jobs page opens, but the newly created job is not selected, highlighted, or opened.

Expected behavior

Users should be able to navigate from the Quick execute success state to the specific job that was just created, so they can immediately inspect its queued/running status and details.

Relevant implementation details

• Quick execute receives the created job ID from api.executeConversation in frontend/src/app/components/ConversationExecutor.tsx.
• The Jobs page is implemented by frontend/src/app/jobs/page.tsx and frontend/src/app/components/JobsManager.tsx.
• Jobs are paginated, so the target job may not be present in the currently loaded page.
• There is currently no dedicated route for an individual job.

Acceptance criteria

• From the Quick execute success state, a user can navigate to the specific newly created job.
• The target job is identifiable even when it is not in the initially loaded Jobs page.
• Reloading or sharing the resulting URL preserves enough context to identify the target job.
• Existing Jobs pagination and job-detail behavior continue to work.
• The interaction is keyboard and screen-reader accessible.