Public/Private workflows and ability to create private workflow from public template

Feature Request

Problem

Currently there's no clear distinction between public and private workflows, and no ability to use a public workflow as a template for creating a private customized version.

Proposed Solution

1. Workflow visibility levels:

• Public workflows - visible and usable by all users
• Private workflows - visible only to the owner

1. Template functionality:

• Allow users to "fork" or "use as template" any public workflow
• Created copy becomes a private workflow owned by the user
• User can then customize the private copy without affecting the original

Use Cases

• Organizations can share workflow templates publicly
• Users can customize workflows for their specific needs without affecting the original
• Enables workflow marketplace/sharing ecosystem

Additional Context

This would enable better workflow sharing and customization patterns in the community.