Workflow Metadata Handling Refactoring

[derekmeegan]

Overview

I realized in the initial implementation that it was a bit convoluted how we handled workflow metadata vs step data, even though they are coming from the same place. The changes focus on using the full Workflow objects directly throughout the component tree rather than extracting and passing metadata separately.

Key Changes

• All components now work with the same workflow data objects
• Components receive the full workflow data instead of just metadata
• Created a unified workflow refresh function that handles both fetching and updating
• Separating extracting metadata from workflow data object from json to flow function
• Move type definitions for sidebar to types file
• API calls for metadata updates are followed by a refresh to ensure consistency

I was not sure if you wanted to still separate updating metadata vs workflow steps on the backend, so I left that intact for now. Let me know if you have any thoughts or feedback.