refactor(api): module live data type

[ahiuchingau]

Overview

This PR defines each module's live data into more specific TypedDicts. Doing so allows us to (1) better visualize what data are expected from the module hardware, (2) simplify the _add_module_substate function in the protocol engine module state store. This is particular important when we are about to add a new module.

I also added from_live_data class generator method to some of the substates (as this is the only time module live data is used). Any concerns regarding pushing this logic down to the individual substate?

[sfoster1]

Looks good, though I'm confused why we would return empty/unknown module data if the validator doesn't pass and not log and ignore it

[vegano1]

oh yeah this will simplify validating the live data

[ahiuchingau]

Looks good, though I'm confused why we would return empty/unknown module data if the validator doesn't pass and not log and ignore it

I'm not sure why either, but I didn't want to change the behavior too much in this PR so i kept it like this.

[CaseyBatten]

This refactor looks good, definitely makes more sense to structure this this way instead of the open returned data structures we had before.