Change todo move API to reference previous uid

[allenporter]

Proposed change

Change todo move API to reference previous uid so that the frontend can sort items without worrying about the ordering for complete vs needs-action items.

This is a partial revert to the original API in #100019 and #102627 with some additional simplifications, so it should be re-reviewed.

This is a breaking change for the todo api, but should be save since it has not been released yet.

This PR needs a frontend PR approved before merge: home-assistant/frontend#18410

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: Update todo move item API to reference previous uid developers.home-assistant#1958
• Link to frontend pull request: Change move item todo API frontend#18410

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.

[MartinHjelmare]

Can we make the previous uid a test parameter instead?

[allenporter]

We don't know it until it is created since uids are created on the fly. We could seed with a fixed database, or mock out uid creation deep in the library, though my thought is that might be too tight of a coupling with an internal detail. However ical does this for it's own tests so there are some util hooks for that.

[allenporter]

(I was replying for ical though same techniques could be used across both)

[MartinHjelmare]

Hmm ok. I guess it's ok like this then.

[MartinHjelmare]

Looks good if we add a note about the meaning of previous uid and when it's None.

[MartinHjelmare]

Can be merged when the frontend PR is approved.

[piitaya]

@MartinHjelmare Frontend PR approved and merged.
Update frontend PR : #102857