Add To-do due date and description fields

[allenporter]

Proposed change

Add To-do due date/time and description fields, with a separate feature entity for each SET_DUE_DATE_ON_ITEM, SET_DUE_DATETIME_ON_ITEM, and SET_DESCRIPTION_ON_ITEM.

These fields will be supported by the following integrations:

• Google Tasks: 'due' (date only) and 'notes' API fields Add due date and description to Google Tasks #104654
• Local To-do: 'due' and 'description' rfc5545 fields (this PR)
• CalDAV: 'due' and 'description' rfc5545 fields Add due date and description to CalDAV To-do #104656
• Todoist: 'due' and 'description' API fields Add due date and description fields to Todoist To-do entity #104655

Example local to-do output:

    - summary: Maintenance item
      uid: f006f6cc-85de-11ee-8c5f-0242ac110002
      status: needs_action
      description: Some description
    - summary: Maintenance item (due date)
      uid: f7c895c8-85de-11ee-8c5f-0242ac110002
      status: needs_action
      due: "2023-11-17"
    - summary: Maintenance item (due date time)
      uid: 25f1dacc-85df-11ee-8f0d-0242ac110002
      status: needs_action
      due: "2023-11-18T06:00:00-08:00"

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Deprecation (breaking change to happen in the future)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request:
  • Add To-do due date/time and description service calls home-assistant.io#29900
  • Add To-do list item due and description field developer documentation developers.home-assistant#1981

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• I have followed the perfect PR recommendations
• The code has been formatted using Black (black --fast homeassistant tests)
• Tests have been added to verify that the new code works.

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

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
• Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[home-assistant]

Hey there @home-assistant/core, mind taking a look at this pull request as it has been labeled with an integration (todo) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of todo can trigger bot actions by commenting:

• @home-assistant close Closes the pull request.
• @home-assistant rename Awesome new title Renames the pull request.
• @home-assistant reopen Reopen the pull request.
• @home-assistant unassign todo Removes the current integration label and assignees on the pull request, add the integration domain after the command.

[allenporter]

From discussion, we do want datetime in the UI. Will mark as draft and have a separate feature flag for date vs datetime.

[home-assistant]

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

[home-assistant]

There is a merge conflict.

[MartinHjelmare]

Thanks!

[MartinHjelmare]

Should this wait for a frontend PR?

[allenporter]

Should this wait for a frontend PR?

I was assuming that it should in case we need any changes, though it does work fine as standalone service calls without UI right now.

[MartinHjelmare]

We've decided to merge this before the frontend work is done. We'll work on the UI design and frontend separately in the next release cycle.

Please solve the merge conflict and then go ahead and merge. Thanks!

Stale

[MartinHjelmare]

I've rebased and fixed some issues after the rebase. When CI passes we can merge.