Allow to use lambda in duration timers of Feedback Cover

**Describe the problem you have/What new integration you would like**

I would like to request the ability to use templates or lambda functions to modify the max_duration, open_duration, and close_duration parameters dynamically in the "Feedback Cover" component. This would allow these parameters to be adjusted through the UI or via automation on the ESP, offering more flexibility in controlling the cover’s behavior.

**Please describe your use case for this integration and alternatives you've tried:**

Currently, the max_duration, open_duration, and close_duration values are fixed and cannot be dynamically adjusted. I would like to be able to change these values based on certain conditions or automations, without needing to manually edit the configuration file. This would be useful for adjusting the timing of the cover's movement based on factors such as temperature, system load, or user input.

For example:

I want to use a slider in the UI to adjust the open_duration in real-time.
I need an automation to adjust the max_duration depending on the status of other devices or sensors.

I have tried using static values, but this approach lacks the flexibility I need.

**Additional context**

Allowing these parameters to be controlled dynamically via templates or lambdas would provide users with more control over the behavior of the "Feedback Cover" component, especially in environments where conditions may change and adjustments are required without needing to reboot or manually change the configuration.

If these changes require a restart of the board to be correctly registered, that would also help resolve the issue.

No files, tests, or entry points are identified in the request. Locate the Feedback Cover component and its max_duration, open_duration, and close_duration configuration, then determine how template or lambda values could be supplied and changed through the UI or automation. Done means those parameters can be adjusted dynamically and the behavior is covered by appropriate tests or documented restart requirements.

Written by the indexing model from the issue text.