Feature/use sqlmodel

[michael-bentz]

What does this change do?

This change refactors orm.py to use SQLModel instead of SQLAlchemy.

Why was this change made?

This change was made to:

• Minimize code duplication. A single type annotation does a lot of work. No need to duplicate models in SQLAlchemy and Pydantic.
• Simplify the developer experience by working directly with objects.

Verification

1. Verify that all automated tests pass.

Affirmations

All of these should have a check by them. Any exception requires an explanation.

• I have added docstrings with details on keyword arguments to new functions following the convention detailed in this gist
• I have added type hinting to new function parameters.
• I have added tests to new functions, following the rules of F.I.R.S.T..
• I matched the style of the existing code.
• I added and updated any relevant documentation (inline, README, CHANGELOG, and such).
• I used Python's type hinting.
• I ran the automated tests and ensured they ALL passed.
• I ran the linter and ensured my changes have not introduced ANY warnings or errors.
• I have made an effort to minimize code changes and have not included any cruft (preference files, *.pyc files, old comments, print-debugging, unused variables).
• I have made an effort maintain a clear commit history (haven't merged other branches or rebased improperly).
• I have written the code myself or have given credit where credit is due.

[saipavan10-git]

Reviewed the code, and ran the test cases. Everything looks fine.