Idempotency warnings removed from triggering documentation

Previously, attaching an idempotency key to wait triggers would sometimes cause parent tasks to become completely stuck, forcing a temporary disabling of the feature in version 3.3.0.

Developers can now safely use idempotency keys when triggering tasks that wait for completion. This restores the ability to ensure complex orchestrating tasks run exactly once without risking stalled executions. The change updates the triggering documentation to reflect that the underlying bug is fixed.