As the context type isn't available in shared worker this method now takes just AuthMetadata. The whole context isn't needed for web anyway now that olmAPI in shared worker can directly call the global identity client.

This previously just contentAccount.mark_keys_as_published(); and was incorrect. We caught it with @kamil during testing.

1. Should we re-cast this to avoid polluting types with any?
2. I prefer any to $FlowFixMe here. There is nothing to fix

Why do we check this for the content account but not the notif account?

to be more specific this is what I meant - but see my comment below

Both accounts are created at the same time, each time keys are rotated synchronously so there is no need to because the result will be the same always (there is no way to eg. rotate content keys but not notifications, those are always in sync).
To make it more readable we can explicitly check both accounts or add a comment explaining this.