aeon_analysis repo structure

[jkbhagatio]

Hi all, as I mentioned in a couple meetings this week, I'd like to turn this repo into a proper python project package.

I'm thinking of organizing this similarly to 'aeon/schema/' in 'aeon_mecha': where we have a 'core' module / subpackage, and additional modules / subpackages for different experiments (e.g. 'social' where we could possibly put in the tube test event detection and analysis code we're working on)

Then there's also the question of where things like @lochhh 's SLEAP training pipeline should live. I could actually see this going in 'aeon/processing/' in 'aeon_mecha' as this notebook contains stuff relevant to model training.

In general, I'd view similar pipelines (if we do similar stuff for spike sorting and/or behavioral syllable detection for instance) as all living in 'aeon/processing'. In particular, for this current SLEAP pipeline, as I go about using it to create a model for the current Social exp mice, I'll try and create module(s) that will fit into 'aeon/processing/'

Let me know what you think.