[flexiglass] Refresh NSSL sensitivity, when the Lockscreen public mode changes

NSSL decides whether it should treat sensitive content differently based
on the AmbientState#isHideSensitive() flag. This flag depends on whether
we have any user profiles in public mode. We don't have a fix callback
to the user profiles for such a change. Instead we query their public
states after various events, when the user profiles might have been
locked/unlocked. These triggers are StatusBarState changes, and the end
of certain animations eg. ScreenLifecycle#onScreenTurnedOff().
With Flexiglass the timing for some of these callbacks have changed, and
we've started triggering a code path, which updates the user profile
public modes without checking whether the NSSL sensitiveness needs
to be refreshed. This caused us to show the private layout of
Notifications until the first user interaction on the Lockscreen.

Bug: 379825109
Test:  lock the device -> notificatins are showing their sensitive content
Flag: com.android.systemui.scene_container

Change-Id: Id6f3daf0f6cf9435f48eb5e5cf73b8a843c3e3b2