[ENH] add code and test to help create schemas

[Remi-Gau]

TODO

• use attrs in all constructors:
  • may require refacrtoring and reordering of class hierarchy with a much leaner parent class
• add doc

unrelated changes

• reordering of imports using precommit
• take tests out of package fodler

[Remi-Gau]

Things are starting to look better.

There is still potential for refactoring but I may wait a bit before doing this.

Want to test it on COBIDAS first and add some doc with sphinx to make sure whoever revisit this will not be thoroughly lost.

[Remi-Gau]

Note that the creation of some files can still be quite involved if they are complex: I still would like to make the API more intuitive but I am not sure how much more I can do for now.

[Remi-Gau]

Note that not all parts of the schema have been covered yet.

FYI: I tend to start from the main one in those and implement the ones that are needed to run some tests to create some example found in the library of the reproschema repo itself

https://www.repronim.org/reproschema/30_schema/

[satra]

@Remi-Gau - we will be getting back to this soon. a new person has joined our group. i wanted to check in on the status.

a few questions:

• is there an intentional reason to move to sphinx from mkdocs?
• there is a README.md in each code folder. this seems quite different from python practices, where such statements would simply be in the code files. (it also makes packaging a little weirder since those files have to be explicitly included).

[Remi-Gau]

@Remi-Gau - we will be getting back to this soon. a new person has joined our group. i wanted to check in on the status.

status after playing around with attrs I indeed started switching to pydantic as I was already adding tons of type hints... but then I had to go back to do other things.

a few questions:

* is there an intentional reason to move to sphinx from mkdocs?

Not really except for the fact that if we want to deploy documentation useful for devs it will be much easier with sphinx given its autodoc features.

* there is a README.md in each code folder. this seems quite different from python practices, where such statements would simply be in the code files. (it also makes packaging a little weirder since those files have to be explicitly included).

yeah those should probably go away and be included as doc strings in the top of the relevant modules

[satra]

thanks @Remi-Gau - there are a few new kid techs on the block that may make our lives even easier. i'll see where we can take this soon.