fix(designer): Sets right run data from repetition for nested components instead of general run data

[ccastrotrejo]

Main Code Changes

• Fixes issues in which run data for nested components wasn't set properly. The data was getting set from the general run data instead of the specific repetition of the parent component. Therefore was showing wrong data.
• New behavior shows the spinner component for nested components and waits for api call from repetition to show it right run data
• Updates Waiting status pill from a static svg to spinner component to add more sense of loading

This pull request includes several changes aimed at improving code maintainability, enhancing functionality, and updating UI elements. The most important changes are grouped by theme below.

• Removed the onRunInstanceSuccess callback from the useRunInstanceStandard hook and moved its logic to a useEffect hook in laDesigner.tsx to simplify the code structure.

• Removed unused import LogicAppsV2 from laDesigner.tsx and OperationCardNode.tsx to clean up the code.

• Replaced the SVG loading spinner with the Fluent UI Spinner component for better consistency and accessibility.

• Added logic to handle run repetition data within a useEffect hook, ensuring that the data is dispatched correctly when available.

Fixes #5167

Both scenarios are set in slooow (10 mbs) download network to be more explicit, but this also happens when workflows are too big and repetition API calls are made after all actions are loaded

Before

Screen.Recording.2024-08-09.at.11.46.56.AM.mov

After

Screen.Recording.2024-08-09.at.11.54.48.AM.mov