Editor vs Runtime: Inconsistent data layer behavior when attaching actors

In editor, data layer system respects the data layer settings for each actor, but at runtime, the condition check is made collectively for each actor cluster, resulting in differences in behavior.

1. Create a world partitioned level
2. Create runtime data layer asset and register it on data layers pane
3. Place 3 static mesh actors into the level
4. First SMA (Parent): Assign the data layer
5. Second SMA (Child 1): Attach to the first SMA on outliner without data layer
6. Third SMA (Child 2):Assign the data layer and attach to the first SMA on outliner
7. Toggle the display checkbox in the data layer panel and confirm that SMA1 and SMA3 respond.
8. Start PIE
9. Enter following command to toggle the data layer and confirm that all SMAs respond

   wp.Runtime.SetDataLayerRuntimeState unloaded [DataLayer asset name]
   

   and

   wp.Runtime.SetDataLayerRuntimeState activated [DataLayer asset name]
   

Result:

Data layer behavior is inconsistent between editor and runtime