Expose actual pipeline trigger type (Manual vs Schedule) as a system property

[Yazdan]

Description:
Currently in Fabric, @pipeline().TriggerType always returns "Manual", even when the pipeline is triggered by a Schedule. This prevents us from detecting at runtime whether a pipeline run is manual or scheduled.

Why this is needed:
Using a static parameter in the schedule trigger is not suitable. We need to detect the pipeline run type dynamically at runtime so that the pipeline can make different decisions depending on whether it was triggered manually or by a schedule.

A manually assigned parameter (e.g., "TriggerSource") does not solve this problem because it does not reflect the actual runtime trigger. Pipelines need to be able to evaluate the trigger type on each run and branch logic accordingly without relying on static values or workarounds.

Request:
Please either:

1. Provide a system property (e.g., pipeline().RunKind) that reliably exposes the actual trigger type at runtime, or

2. Fix the bug so that @pipeline().TriggerType correctly returns "Schedule" for scheduled runs.

This would allow pipelines to dynamically adapt their logic in a reliable way.

Thanks

[Yazdan]

Update: Recently, I tested this again with the latest Fabric updates and found that this issue has been resolved 🎉. Now, when a pipeline is triggered by a schedule, the value of @pipeline().TriggerType correctly returns "1" instead of always showing "Manual".

Thanks to the Fabric team for addressing this!