Preserve typed ObjectState history across restarts

[trissim]

Summary

• persist ObjectState history with dill so Paths, enums, dataclasses, callable objects, and graph identity survive application restarts
• remove the obsolete JSON compatibility import paths instead of maintaining a second lossy persistence contract
• derive documentation release metadata from the package and add typed-history regression coverage
• release ObjectState 1.0.23

Verification

• 160 ObjectState tests passed on Python 3.13
• no Ruff diagnostics on added lines
• full fatal Ruff checks passed
• real initialized OpenHCS GUI history saved and restored with typed Paths and an edited nested UIConfig field
• sdist and wheel built; twine check passed

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[augmentcode]

^{PR Risk Analyzer Agent🛡️}

👀 Human Input Needed
A pair-review briefing is ready for you.

→ Pair Review Briefing

[augmentcode]

^{Deep Code Review Agent🐛}

Review completed with 2 suggestions.

[augmentcode]

^{Deep Code Review Agent🐛}

The README example now points users at history.objectstate, but docs/undo_redo.rst still documents save_history_to_file() / load_history_from_file() as JSON persistence. That generated documentation will describe the removed JSON contract after this PR, which can mislead users into treating the new dill file as portable JSON.

Severity: low

---

_{🤖 Was this useful? React with 👍 or 👎}

[augmentcode]

^{Deep Code Review Agent🐛}

This helper leaves the typed_history ObjectState registered in ObjectStateRegistry._states, so later tests in the same process can capture it in unrelated snapshots or import histories against the wrong scope set. Because the registry is global and conftest.py does not reset it between tests, this persistence test can make the suite order-dependent.

Severity: medium

---

_{🤖 Was this useful? React with 👍 or 👎}