importing cycler data to PyBOP notebook example added

[Dibyendu-IITKGP]

Description

A example notebook file is added to demonstrate how to import battery cycler data directly to PyBOP without any pre-processing. Battery-Data-Toolkit is used for this purpose. However, a similar kind of approach can be followed for any battery cycler data converter (example: cellpy etc.). It is also shown how to use part of the cycler data to fit HPPC pulses and estimate equivalent circuit parameters.

Issue reference

Fixes #504

Review

Before you mark your PR as ready for review, please ensure that you've considered the following:

• Updated the CHANGELOG.md in reverse chronological order (newest at the top) with a concise description of the changes, including the PR number.
• Noted any breaking changes, including details on how it might impact existing functionality.

Type of change

• [ ] New Feature: A non-breaking change that adds new functionality.
• [ ] Optimization: A code change that improves performance.
• [ ] Examples: A change to existing or additional examples.
• [ ] Bug Fix: A non-breaking change that addresses an issue.
• [ ] Documentation: Updates to documentation or new documentation for new features.
• [ ] Refactoring: Non-functional changes that improve the codebase.
• [ ] Style: Non-functional changes related to code style (formatting, naming, etc).
• [ ] Testing: Additional tests to improve coverage or confirm functionality.
• [ ] Other: (Insert description of change)

Key checklist:

• [ ] No style issues: $ pre-commit run (or $ nox -s pre-commit) (see CONTRIBUTING.md for how to set this up to run automatically when committing locally, in just two lines of code)
• [ ] All unit tests pass: $ nox -s tests
• [ ] The documentation builds: $ nox -s doctest

You can run integration tests, unit tests, and doctests together at once, using $ nox -s quick.

Further checks:

• [ ] Code is well-commented, especially in complex or unclear areas.
• [ ] Added tests that prove my fix is effective or that my feature works.
• [ ] Checked that coverage remains or improves, and added tests if necessary to maintain or increase coverage.

Thank you for contributing to our project! Your efforts help us to deliver great software.

[Dibyendu-IITKGP]

@BradyPlanden I think with this example, we can remove previously added equivalent_circuit_identification_hppc.ipynb and equivalent_circuit_identification_multipulse.ipynb files. This file serves all the purposes of the mentioned files. Also, I think I can add within the same file how to use cellpy (as an alternative to Battery-Data-Toolkit) for reading cycler data. Let me know your thoughts.

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 99.05%. Comparing base (46ae507) to head (5c6c8a2). Report is 10 commits behind head on develop.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## develop #522 +/- ## ======================================== Coverage 99.04% 99.05% ======================================== Files 52 52 Lines 3578 3582 +4 ======================================== + Hits 3544 3548 +4 Misses 34 34 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.