Unified Certificate Handling: Identical Configuration for Tasks and Triggers

Currently, certificate handling is implemented and configured differently across Tasks and Triggers. I propose that these be made functionally and visually identical. Key Requirements: Identical Configuration: The fields, settings, and UI components should be exactly the same whether configuring a Trigger or a Task. Functional Parity: The underlying logic for how certificates are resolved, loaded, and validated must be standardized across the entire platform. User Recognition: Users should be able to apply the exact same workflow everywhere without having to relearn different logic for different components. Goal: To create a seamless and predictable developer experience where certificate management is consistent in both form and function.