feat(ui): add previous runs section to sensor details page

[puretension]

Fixes #14809

Motivation

Sensor details page lacks Previous Runs visibility, making it difficult for users to locate and monitor workflows triggered by sensor events. This creates inconsistent UX compared to CronWorkflow which provides clear Previous Runs section.

Modifications

• Added Previous Runs section below Sensor editor tabs using workflows.argoproj.io/sensor label filtering
• Implemented identical UI pattern as CronWorkflow with WorkflowDetailsList component for consistency
• Fixed empty state handling with proper array length check to display triggered workflows correctly

recoreded_video.mov

Verification

• Sensor details page now displays Previous Runs section with triggered workflows
• Workflows are properly filtered by workflows.argoproj.io/sensor=sensor-name label
• Empty state shows appropriate message when no workflows exist
• UI matches CronWorkflow Previous Runs behavior for consistent user experience

Documentation

No documentation changes needed as this follows existing CronWorkflow Previous Runs pattern that users are already familiar with.

[Joibel]

This file shouldn't be in this PR.

[puretension]

@Joibel Fixed! I removed the incorrect file from the PR. It was accidentally included from a wrong branch merge.
(I think it came my previous work - #14816)

[Copilot]

Pull Request Overview

This PR adds a "Previous Runs" section to the Sensor details page to display workflows triggered by sensors, improving UX consistency with CronWorkflow details page.

• Added workflow fetching using workflows.argoproj.io/sensor label to retrieve sensor-triggered workflows
• Implemented Previous Runs UI using WorkflowDetailsList component matching CronWorkflow pattern
• Added label constant for sensor workflows to shared models

Reviewed Changes

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

File	Description
ui/src/sensors/sensor-details.tsx	Added workflow list fetching and Previous Runs section display with ZeroState handling
ui/src/shared/models/workflows.ts	Added sensor label constant for filtering sensor-triggered workflows
ui/src/workflow-templates/workflow-template-list.tsx	Unrelated changes: Added label persistence and URL query param handling
.features/pending/14809-sensor-previous-runs.md	Feature documentation for the sensor Previous Runs addition

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The condition !workflows will always be false since workflows is initialized to [] on line 36. The check should be workflows.length === 0 only, matching the pattern in cron-workflow-details.tsx which checks !workflows where workflows is initialized to undefined.

Suggested change

	{!workflows || workflows.length === 0 ? (
	{workflows.length === 0 ? (

[Copilot]

Missing error handling for the async workflow fetching. If services.workflows.list() or services.info.getInfo() fails, the error is not caught or displayed to the user. Add .catch(setError) or wrap in try-catch to handle potential errors, similar to the sensor fetching useEffect on line 66-72.

Suggested change

	const workflowList = await services.workflows.list(namespace, null, [`${models.labels.sensor}=${name}`], {limit: 50});
	const workflowsInfo = await services.info.getInfo();
	setWorkflows(workflowList.items);
	setColumns(workflowsInfo.columns);
	try {
	const workflowList = await services.workflows.list(namespace, null, [`${models.labels.sensor}=${name}`], {limit: 50});
	const workflowsInfo = await services.info.getInfo();
	setWorkflows(workflowList.items);
	setColumns(workflowsInfo.columns);
	setError(null);
	} catch (err) {
	setError(err);
	}

[piby180]

Hi, thanks for working on it. Any update?