Standardize model __repr__ functions

[michplunkett]

Description of Changes

Addressed inconsistencies with the model __repr__ functions.

Mostly making this because this PR got a bit out of control: #1138

Tests and Linting

• This branch is up-to-date with the develop branch.
• pytest passes on my local development environment.
• pre-commit passes on my local development environment.

[AetherUnbound]

Looks good but there are a few more inconsistencies that might be good to address I think!

[michplunkett]

Thanks for the eye, @AetherUnbound! I'll address those tomorrow and get back to you when they're done.

[b-meson]

I don't know enough about Python to feel super comfortable reviewing it so I'll let the rest of the reviewers weigh in!

[sea-kelp]

Other than the inconsistencies Madison pointed out, this looks good! If we're being pedantic, the Python spec technically says you should be able to instantiate the object by eval-ing the string returned by __repr__
https://docs.python.org/3/library/functions.html#repr

I also wonder if we could get these for free by just making our model classes dataclasses: https://docs.sqlalchemy.org/en/20/orm/dataclasses.html

[michplunkett]

These are all good comments, thank you!

Please excuse the delay in my response, I've been holday'ing. I'll take a look at the MappedAsDataclass class tomorrow. If we could remove the need to update the __repr__ function and always be up to spec, that feels like the right way to go. I'll ping y'all when I have an update in place. 🧐

[michplunkett]

Looking at the changes needed to implement the MappedAsDataclass class, @sea-kelp, I am going to make these updates using two PRs:

1. Update with the changes that @AetherUnbound pointed out.
2. Update SQL Alchemy from 1.4.52 -> 2.x.y and then add the MappedAsDataclass addition.