Fix composite step kind not applied due to flags not copied in ResolvedStepDefinition

[Copilot]

ResolvedStepDefinition extends StepDefinition but its constructor only forwarded the five base fields to super(...), silently dropping composite, deprecated, and dynamic flags. This meant CompletionItemService.asCompletionItem() always saw isComposite() == false, so composite steps were always rendered with CompletionItemKind.Method instead of CompletionItemKind.Function.

Changes

• ResolvedStepDefinition: Copy composite, deprecated, and dynamic flags from the source StepDefinition after the super(...) call:

  setDeprecated(stepDefinition.isDeprecated());
  setComposite(stepDefinition.isComposite());
  setDynamic(stepDefinition.isDynamic());

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Add possibility to differentiate built-in steps from composite ones in VS Code</issue_title>
<issue_description>As a QE
When I write/read Test Automation in VIVIDUS
I want to see which steps are built-in and which are Composite
So that it is clear which steps are being used

This will increase readability as well as help newcomers understand the code in already created repositories as they may be not aware of the full list of built-in steps
Currently all steps are being highlighted the same way and there's no way to differentiate the steps unless you remember them all or use Search or ./gradlew printSteps which is time consuming</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Add possibility to differentiate built-in steps from composite ones in VS Code #928

---

🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.