Add segment annotation mode to edit_physio()

[me-pic]

Closes #

[WIP]
I modified the peakdet codebase a moment ago to be able to annotate segments (save the onset and offset of segments) during the manual editing (operations.edit_physio) for my personal use case. I'm doing that PR in case that could be a feature useful for others!

Proposed Changes

• Add annotate_segments() function and modify existing functions in editor.py to be able to annotate segments in the interactive viewer
• Add a segments property to be able to store the onset and offset of selected segments in the segments attribute of a Physio instance, and in the metadata
• Modify the docs to add information relative to the 'annotation mode'

A few comments/questions:

• I had to modify the .pre-commit-config.yaml file and specify the python version to be able to run the pre-commit hooks. Ideally I guess the .pre-commit-config.yaml would not include it, so if anybody wants to discuss the error I got before that change, it would be great!
• I had to manually skip the check-added-large-files hook to be able to commit the physio_edit_segment.gif for the documentation (the file size is smaller than the other gif already included i.e. physio_edit.gif).
• I wasn't able to build the documentation locally as is (via make html in the docs/ subdirectory). There was a problem with L118 in conf.py. I ended up just commenting that line for the sake of testing the rendering of the modified doc. I would have to investigate a bit more on that, but it's also been a while since the last rtd build (5 years ago) and I'm wondering if the problem is not only local.
• For the annotation itself, the current behavior of that mode doesn't allow for overlapping segment. If you have a segment and you select one that overlap, the previous segment will be removed and only the last segment will remain. Happy to make the changes to allow such behavior depending on what would be the most useful to others!

Change Type

• bugfix (+0.0.1)
• minor (+0.1.0)
• major (+1.0.0)
• refactoring (no version update)
• test (no version update)
• infrastructure (no version update)
• documentation (no version update)
• other

Checklist before review

• I added everything I wanted to add to this PR.
• [Code or tests only] I wrote/updated the necessary docstrings.
• [Code or tests only] I ran and passed tests locally.
• [Documentation only] I built the docs locally.
• My contribution is harmonious with the rest of the code: I'm not introducing repetitions.
• My code respects the adopted style, especially linting conventions.
• The title of this PR is explanatory on its own, enough to be understood as part of a changelog.
• I added or indicated the right labels.

• I added information regarding the timeline of completion for this PR.

• Please, comment on my PR while it's a draft and give me feedback on the development!