fix(designer): fix issue where scope nodes didn't get focused when they were jumped to

[hartra344]

This pull request primarily focuses on improving the user interaction with the ScopeCard component in the libs/designer-ui package. The changes introduced include the addition of a focus state for the ScopeCard and the use of optional chaining for runData properties.

Here are the most important changes:

User Interaction Improvement:

• libs/designer-ui/src/lib/card/scopeCard/index.tsx: Implemented a focus state for the ScopeCard by using useRef and useEffect hooks from React. This allows the card to be focused programmatically when the setFocus prop is true. [1] [2] [3]
• libs/designer/src/lib/ui/CustomNodes/ScopeCardNode.tsx: Added the useShouldNodeFocus hook to determine whether the ScopeCard should be focused, and passed the result as the setFocus prop to the ScopeCard component. [1] [2] [3]

Codebase Simplification:

• libs/designer-ui/src/lib/card/scopeCard/index.tsx: Used optional chaining for runData properties to simplify the code and prevent potential runtime errors.

The changes in this pull request will enhance the user experience by providing visual feedback when a ScopeCard is focused, and improve the codebase by preventing potential errors related to runData properties.