Removing @benadida's change to make the provisioning mock's setStatus...

Removing @benadida's change to make the provisioning mock's setStatus asynchronous.  Instead of generating the key whenever the status is set, generate the key whenever the user is being provisioned.  Since the mock uses jwcrypto which must be seeded, seed jwcrypto with some bits.  This more closely matches what a real RP would do.

In the unit tests, any asynchronous calls to provisioningMock.setStatus have been make synchronous.

In user.js, syncEmailKeypair, since jwcrypto depends on there being a seed to generate a keypair, call network.withContext which ensures there is a seed.