suppport for SQL backend

[AadilLatif]

Preliminary Checks

• I have searched existing issues for a duplicate feature request and I'm sure this is new.
• I have read and followed the docs and still think this is missing.

Description

@daniel-thom can this be supported in infrasys?

1. SQLmodel can potentially be leveraged to build tables for nested Components.
2. How would we handle pint quantities that can be a float or an array.
3. Potential to manage time-series data in the same file?

[daniel-thom]

Is this a question of serialization or of the in-memory data structures? For example, when the user calls system.get_component() today, the code retrieves a component object from a dictionary. Would you want this call to translate to a SQL query that de-serializes a database row into the component class? This would be a lot of work and the code would certainly be slower. If the question only relates to serialization, yes, we can absolutely do this. Instead of system.to_json() there is system.to_sql(). There are lots of questions about how components are stored with primary/foreign key relationships, but we can work through them.

It is possible to store time series data in the same database. We already support something like this with the chronify time series storage class. We store the data in a DuckDB or SQLite database. We could add new tables for components.