Expected:
When a controller is disconnected and reconnected, InputActions should gracefully resume

Observed:
When a controller is disconnected and reconnected, InputActions do not continue to fire. Sometimes updates through the Input Debugger do not resume either.

When Vive controllers are disconnected and reconnected, they do not resume sending updates. Unfortunately, there is not a single reproduction procedure that always works, but there are several that give a high degree of probability of reproduction.

Reproduction project:
https://oc.unity3d.com/index.php/s/dxjIKi1TMPXnCER

If controller is off when app starts, it doesn't get picked up.
Steps to reproduce:
- Set up Vive
- turn off both controllers
- Press play
- Turn on both controllers
- move thumbs across both controller touchpads, observe correct reporting
- move thumb across the controller touchpads one at a time, observe no input reporting through scene UI or the Input Debugger.

Steps to reproduce:
- Start application
- Observe Vive controller information updating correctly.
- Turn controller off and on again
- Observe that input is no longer reporting.

Steps to reproduce:
- Set up Vive HMD.
- Hide hmd and controllers from tracking. In SteamVR the HMD visual will turn dark and the controllers will be blinking.
- Keep the controllers hidden from tracking. Press play. Observe the controller input working correctly for the New Input System.
- Keep the controllers hidden from tracking. Turn both Vive controllers off and on again. Observe no input.
- Expose the controllers to tracking. Observe InputSystem null errors. Observe that there are no updates.