Allow to init CellMorphologyProtocol directly

[GianlucaFicarelli]

This PR is a proposal to allow the user to init CellMorphologyProtocol directly, so that the create and retrieve code is symmetric, because in this way the same class class can be used.

Instead of

morphology_protocol = DigitalReconstructionCellMorphologyProtocol(...)
protocols = client.search_entity(entity_type=CellMorphologyProtocol).all()

now it would be possible to use CellMorphologyProtocol and specify generation_type:

morphology_protocol = CellMorphologyProtocol(
  generation_type=CellMorphologyGenerationType.digital_reconstruction, ...
)
protocols = client.search_entity(entity_type=CellMorphologyProtocol).all()

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

Flag	Coverage Δ
pytest	99.94% <100.00%> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
src/entitysdk/models/__init__.py	100.00% <100.00%> (ø)
src/entitysdk/models/cell_morphology_protocol.py	100.00% <100.00%> (ø)
src/entitysdk/route.py	100.00% <ø> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[eleftherioszisis]

My only concern is if someone would want to use the CellMorphologyProtocol without automatically adapting it. Maybe this is not something desired with the protocols. LGTM otherwise

[mgeplf]

ok by me