dedup

In D11335#327425, @michal wrote:

Looks good on the identity-service-client-proxy part.

Short explanation is -> we are moving the identity client to worker so that multiple tabs can synchronize the identity calls between them and not conflict. identity-service-client-wrapper.js will run on web worker and identity-service-client-proxy.js will run in the tab JS context and pass the method calls to the worker (we didn't "flip the switch" yet so for now the identity-service-client-wrapper.js is still running in the tab JS context though).

need to dedup a little

address feedback on previous revision

after rebasing i started getting a flow error. updated web/grpc/identity-service-client-proxy.js to resolve it, but not really sure what this code does... going to add @michal as a reviewer

setting @ashoat as blocking

rebase

rebase on top of prekey format diffs

1. What's "retagging" mean and why was it necessary here?

fix typo in allow origin list

set image tag conditionally so that we can use different images for staging and production

ah remembered why i didn't do this right away... i need to first land the rest of the stack and cut a new release

In D11257#325183, @ashoat wrote:

Should this stack include a diff to bring us back to having two parallel identity instances in production?

In D11256#325184, @will wrote:

Looks good to me. We're removing the cache to support stateless sessions correct?

i've updated D11255 to use DeleteItem in get_workflow(). Now the function retrieves and removes the workflow, so we don't run the risk of retrieving it multiple times

use DeleteItem instead of GetItem

In D11256#325134, @michal wrote:

1. We no longer invalidate the cache. What happens if a client calls _finish method a second time?

fix serialization/deserialization of Login struct

agree with @kamil 's suggestions, but lgtm otherwise