Fix workspace callback binder lifecycle (2/2)

Every time the app is paused and resumed, the workspace callback binder
would launch new coroutines, even though the old coroutine scope was not
yet cancelled, resulting in many extra messages being sent to Launcher
and Keyguard. This is because the workspace callback binder is launching
coroutines using the fragment lifecycle start and stop, even though it is
binded in the surfaceCreated function. Adjust to follow the surface's
lifecycle.

Also adjust to use view lifecycle in the fragment where appropriate.

Flag: com.android.systemui.shared.new_customization_picker_ui
Bug: 384765903
Test: manually verified with print statements
Change-Id: Ie965c643c9a1e65dd9d0053f401f702a875ddd95