fix: generate-task-trigger-id

[hemantmm]

closes: #8921

What changes are being made and why?

✅ Added automatic ID generation for tasks and triggers in the No-Code editor when the user does not specify an ID.
✅ IDs follow the pattern "task1", "task2", "trigger1", etc., incrementing based on existing elements.
✅ Updated TaskEditor to assign an auto-generated ID immediately when a new task/trigger is created or a type is selected.
✅ Ensured backend allows saving flows with tasks/triggers that have no user-specified ID.

---

Fix:

Updated UI components and logic so that:

• When a user creates a new task or trigger without specifying an ID, the editor generates a unique sequential ID (e.g., "task3", "trigger2").
• The ID is injected into the YAML before saving or updating the flow.
• Validation gracefully handles missing IDs and allows saving.

This improves UX by ensuring all tasks/triggers have valid IDs, even if the user omits them, and aligns with backend requirements.

[hemantmm]

@elevatebart, can you review this PR?