[Feature] Implement Status & Running Hours Inheritance for Parent-Child Assets

[romiramadhan24]

There is an issue with how Parent Assets (e.g., A000042 - Washing Line) and their Child Assets (e.g., Wet Crusher, Conveyor, Metal Detector) handle status changes and Running Hours tracking.

Currently, Parent and Child assets are creating data anomalies where child assets continue running while the parent asset is stopped.

Current Behavior vs Expected Behavior

Feature	Current Behavior	Expected Behavior
Status Dependency	When a Parent Asset's status is changed to STANDBY or OFFLINE, its Child Assets retain their active status and do not automatically cascade down.	Setting Parent to STANDBY / OFFLINE automatically cascades the same status to all Child Assets.
Asymmetric Operation	Child Assets cannot be set to STANDBY, SCHEDULED MAINTENANCE, or DOWN while assigned to a Parent Asset, even when the Parent is OPERATIONAL.	Child Assets can be set to independent statuses (e.g., STANDBY, SCHEDULED MAINTENANCE, DOWN) when the Parent Asset is OPERATIONAL to allow maintenance or equipment bypass.
Running Hours Calculation	Child Assets accumulate running hours even when Parent is STANDBY or DOWN, causing Child Hours > Parent Hours.	Running hours timer pauses for Child Assets whenever Parent is not operational or when the individual Child is standby or down.

Parent Asset

Child Asset