[ENH] add a difference transformer to series transformations

[TinaJin0228]

Reference Issues/PRs

fixes #1553

What does this implement/fix? Explain your changes.

This implements a transformer that computes the n-order differences of a time series.

The input time series is expected to have a NumPy inner-type, and the transformation is performed using numpy.diff().

To preserve the original shape of the series along the time axis, the first order element(s) of the output are filled with NaN.

Does your contribution introduce a new dependency? If yes, which one?

No. It only depends on NumPy.

Any other comments?

No.

PR checklist

For all contributions

• I've added myself to the list of contributors. Alternatively, you can use the @all-contributors bot to do this for you after the PR has been merged.
• The PR title starts with either [ENH], [MNT], [DOC], [BUG], [REF], [DEP] or [GOV] indicating whether the PR topic is related to enhancement, maintenance, documentation, bugs, refactoring, deprecation or governance.

For new estimators and functions

• I've added the estimator/function to the online API documentation.
• (OPTIONAL) I've added myself as a __maintainer__ at the top of relevant files and want to be contacted regarding its maintenance. Unmaintained files may be removed. This is for the full file, and you should not add yourself if you are just making minor changes or do not want to help maintain its contents.

For developers with write access

• (OPTIONAL) I've updated aeon's CODEOWNERS to receive notifications about future changes to these files.

[aeon-actions-bot]

Thank you for contributing to aeon

I have added the following labels to this PR based on the title: [ $\color{#FEF1BE}{\textsf{enhancement}}$ ].
I have added the following labels to this PR based on the changes made: [ $\color{#41A8F6}{\textsf{transformations}}$ ]. Feel free to change these if they do not properly represent the PR.

The Checks tab will show the status of our automated tests. You can click on individual test runs in the tab or "Details" in the panel below to see more information if there is a failure.

If our pre-commit code quality check fails, any trivial fixes will automatically be pushed to your PR unless it is a draft.

Don't hesitate to ask questions on the aeon Slack channel if you have any.

PR CI actions

These checkboxes will add labels to enable/disable CI functionality for this PR. This may not take effect immediately, and a new commit may be required to run the new configuration.

• Run pre-commit checks for all files
• Run mypy typecheck tests
• Run all pytest tests and configurations
• Run all notebook example tests
• Run numba-disabled codecov tests
• Stop automatic pre-commit fixes (always disabled for drafts)
• Disable numba cache loading
• Push an empty commit to re-run CI checks

[TinaJin0228]

It seems that one of the automated checks failed with errors indicating it couldn't find the merge base or my commit SHA:

Warning: Unable to find merge base between 45d0390d1a441264943f8963547409bb36935d2d and 8f78ec98e57b49640bd59f5570f35efb9fea7e67
Error: Unable to locate the commit sha: 45d0390d1a441264943f8963547409bb36935d2d
Error: Please verify that the commit sha is correct, and increase the 'fetch_depth' input if needed
Warning: fatal: bad object 45d0390d1a441264943f8963547409bb36935d2d
Warning: If this pull request is from a forked repository, please set the checkout action `repository` input to the same repository as the pull request.
Warning: This can be done by setting actions/checkout `repository` to ${{ github.event.pull_request.head.repo.full_name }}

[MatthewMiddlehurst]

Thanks, few comments.

[TinaJin0228]

I have made som modifications according to your comments. @MatthewMiddlehurst

[TinaJin0228]

I have made som modifications according to your comments. @MatthewMiddlehurst

@MatthewMiddlehurst I am wondering if you could give it a quick look when you get a chance? Thanks!

[MatthewMiddlehurst]

LGTM for the most part, just one documentation bit.

[MatthewMiddlehurst]

Don't need this part, it should be all documented higher up in the base class axis parameter stuff