[mattcasters]

Creating a workflow from the file explorer context menu built an empty workflow and saved it. File > New still added a Start action. Both paths now use HopWorkflowFileType.addDefaultStartAction, so a new workflow contains a Start action named Start at (50, 50). The saved file includes that action.

fixes #9091

---

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

• Run mvn clean install apache-rat:check to make sure basic checks pass. A more thorough check will be performed on your pull request automatically.
• If you have a group of commits related to the same change, please squash your commits into one and force push your branch using git rebase -i.
• Mention the appropriate issue in your description (for example: addresses #123), if applicable.

To make clear that you license your contribution under the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

• I hereby declare this contribution to be licensed under the Apache License Version 2.0, January 2004
• In any other case, please file an Apache Individual Contributor License Agreement.

[bamaer]

@mattcasters thanks, sharing the helper between File > New and the explorer is the right fix.

Built in a scratch copy (ui with -am) and ran HopWorkflowFileTypeTest: passes. "Create file..." already excludes workflow types, so the explorer's "Create workflow..." was the only route creating an empty workflow. No blockers from my side.

Code reviewed and unit test run; not exercised in the GUI.