Feature add last_operation to time based cover

[xprofiler]

What does this implement/fix?

I need to know the last operation of the cover when handle a cover STOP command, because the current_operation is already set to IDLE. With the last operation information I am able to decide which of the two buttons (UP and DOWN) for my Warema controller I have to press to stop the cover.

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Other

Related issue or feature (if applicable): fixes esphome/issues#4252

Test Environment

• ESP32
• ESP32 IDF
• ESP8266
• RP2040
• BK72xx
• RTL87xx

Example entry for config.yaml:

cover:
  - platform: time_based
    name: "Sunblind AZ"
    id: sunblind_az
    open_action:
      - button.press: az_h
    open_duration: 34s
    close_action:
      - button.press: az_r
    close_duration: 32.5s
    stop_action: 
      - lambda: !lambda |-
          if (id(sunblind_az).last_operation() == CoverOperation::COVER_OPERATION_IDLE) {
            // Cover is idle
          } else if (id(sunblind_az).last_operation() == CoverOperation::COVER_OPERATION_OPENING) {
            // Cover is currently opening
            id(az_r).press();
          } else if (id(sunblind_az).last_operation() == CoverOperation::COVER_OPERATION_CLOSING) {
            // Cover is currently closing
            id(az_h).press();
          }
    has_built_in_endstop: true

Checklist:

• The code change is tested and works locally.
• Tests have been added to verify that the new code works (under tests/ folder).

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated in esphome-docs. See Update time_based.rst - handle with last operation esphome-docs#3532

[probot-esphome]

Hey there @esphome/core, mind taking a look at this pull request as it has been labeled with an integration (logger) you are listed as a code owner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[probot-esphome]

Hey there @esphome/core, mind taking a look at this pull request as it has been labeled with an integration (esp32) you are listed as a code owner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[probot-esphome]

Hey there @OttoWinter, mind taking a look at this pull request as it has been labeled with an integration (api) you are listed as a code owner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[probot-esphome]

Hey there @kroimon, mind taking a look at this pull request as it has been labeled with an integration (tt21100) you are listed as a code owner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[xprofiler]

I created my feature branch from tag https://github.com/esphome/esphome/tree/2023.12.5 because this is my docker containers version and the version I tested my changes.

[kroimon]

Please rebase your branch onto the latest dev branch, there are a lot of unrelated changes in this PR.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 53.45%. Comparing base (4d8b5ed) to head (9a8edc6).
Report is 470 commits behind head on dev.

Additional details and impacted files

@@            Coverage Diff             @@
##              dev    #6084      +/-   ##
==========================================
- Coverage   53.70%   53.45%   -0.26%     
==========================================
  Files          50       50              
  Lines        9408     9543     +135     
  Branches     1654     1685      +31     
==========================================
+ Hits         5053     5101      +48     
- Misses       4056     4131      +75     
- Partials      299      311      +12     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[xprofiler]

For some reason a normal rebase was not possible, so I recreated my feature branch derived from the current dev branch and make this one line change to corresponding file. I will try to test it with a current build.