chore: Use implicit default loading rather than explicit joined eager loading

[john-bodley]

Description

A rehash of #1959 but, per #1959 (comment), rather than explicitly defining the form of the relationship loading rely instead on the implicit definition of the specific model relationships (which defaults to lazy per here). This helps to ensure that the optimal loading technic is used for each specific implementation/use case.

See Relationship Loading Techniques for the various relationship loading techniques which are supported by SQLAlchemy which fall into one of three categories: lazy, eager, or none. Lazy implies delayed loading and results in N +1 queries, whereas eager loading "eagerly" loads items alongside the parent—either using a separate SELECT statement or using JOIN clause (which can lead to a multiplicative issue when the parent has multiple relationships).

ADDITIONAL INFORMATION

• Has associated issue:
• Is CRUD MVC related.
• Is Auth, RBAC security related.
• Changes the security db schema.
• Introduces new feature
• Removes existing feature

[dpgaspar]

Awesome I like this approach. Thank you!