Add a slightly longer sleep to a test that waits for a timer to advance

[jmhooper]

The sign in spec changed in this commit waits for a timer to advance. It waits exactly 1 second, which near the boundaries of the current second can lead to an edge case that leads to the following failure:

Failures:
  1) Sign in session approaches timeout user sees warning before session times out
     Failure/Error: expect(time2).to be < time1
       expected: < "14 minutes and 56 seconds"
            got:   "14 minutes and 56 seconds"
     # ./spec/features/users/sign_in_spec.rb:274:in `block (3 levels) in <top (required)>'
     # ./spec/rails_helper.rb:134:in `block (2 levels) in <top (required)>'

This commit modifies the sleep in this test to advance more than a second so that the assertion never runs near the boundary of the recent second.

[jskinne3]

Best 2-byte commit ever

[aduth]

I don't suppose there's any way to avoid a real-time sleep and use something like Rails simulated time travel? Would be nice to avoid additional delays in the specs.

[jmhooper]

I agree, but there isn't anything obvious since this is waiting on the timer in the JS running in chromedriver. This commit fixes the flaky test and trades a half second for not having to wait for an entire 1/11 of the suite re-run.