Split up max_duration of endstop cover into max_duration_close and max_duration_open.

**Describe the problem you have/What new integration you would like**
Split up max_duration of endstop cover into max_duration_close and max_duration_open.

**Please describe your use case for this integration and alternatives you've tried:**
I have built a simple chicken door that is driven by a dc motor with a gearbox and a pulley and the door has two endstops. The pulley and the door are connected with a rope. Sometimes the chicken manage to get bedding into the guide rails and therefore the close endstop is not triggered and the pulley is turning until the door is nearly closed and then it's going up until max_duration is reached. Due to gravitation, the times for opening and closing are very different. A high value for max duration ensures the opening in the morning, but has the risk that the door does not close properly at night.
I have played around with motor speed and the max_duration value, but did not find any combination that worked well. Different max_duration times would solve my problem.

**Additional context**

No implementation files, tests, or entry points are named in the request. Start by locating the endstop cover implementation and its existing max_duration handling, then determine how separate opening and closing limits should be configured and applied. Done means opening and closing each honor their own maximum duration without breaking endstop behavior.

Written by the indexing model from the issue text.