Add Support for re-running Custom Confirmation Logic

[RealmBot]

Expose work done in Expose Retry Custom Confirmation Client API endpoint within Realm's JS SDK.

This endpoint to send the user confirmation email. 

This will alleviate this type of problems:
{quote}At Realm Web SDK, there is no method for "Resend confirmation for Function based user confirmation" at Email/Password provider.

I tried calling "app.emailPasswordAuth.resendConfirmationEmail" but it returns:
please use confirm via function (status 400)

Which would be correct. So looked in source code and tried to find the equivalent for function, but there is no such method.

Could you please provide a fix, I have the situation where users who created the account, and forgot to click the confirmation email, are never confirmed, and never able to login.

Version of Realm and Tooling
Realm JS SDK Version: Realm Web 1.0
Node or React Native: No
{quote}

[RealmBot]

➤ On 2020-06-25, Drew DiPalma commented:

Out of curiosity – what is this blocked on?

[RealmBot]

➤ Kræn Hansen commented:

[~drew.dipalma] I don't think it's blocked? But I would for us to learn a bit more about the need for this feature and the API exposed by the server to help move this forward accordingly.
[~martin.burdette] do you have details on what this endpoint on the server does and how its supposed to be called?
[~jason.flax] do you have details on where in the SDKs API this would be good to be exposed?

[RealmBot]

➤ Martin Burdette commented:

hey I'm happy to help here if you want to hop on a call/ slack or something sometime, Or I can just try to answer questions here, let me know! (sorry for the slow reply)

[RealmBot]

➤ Ian Ward commented:

[~brian.munkholm] Can we get this added to the next sprint please?

[sync-by-unito]

➤ Kenneth Geisshirt commented:

[~ian.ward] Sorry for the late reply. I will add it to the next release to get it more visible.

[sync-by-unito]

➤ Drew DiPalma commented:

What's the latest status here? This keeps coming up as a frequent pain point.

[sync-by-unito]

➤ Sumedha Mehta commented:

relevant concern from developer - #3430

[kraenhansen]

This is what needs to be done for Realm Web:

• Add the "/confirm/call" route to the routes.ts named confirmCall.
• Add a method on the EmailPasswordAuth class named retryCustomConfirmation (this is the name suggested by Realm Java) which calls the server using the confirmCall route.
• Bonus: Add a test.

This is what needs to be done for Realm JS:

• Add a retry_custom_confirmation to the /src/js_email_password_auth.hpp which calls the retry_custom_confirmation exposed by Object Store.
• Expose the promisified version in /lib/email-password-auth-methods.js and the Chrome debugger /lib/browser/email-password-auth.js (and here)
• Bonus: Add a test.

[sync-by-unito]

➤ Stoney Burks commented:

Moving this to RFW so Franck can focus on shipping Hermes Support. We will pick this back up after Hermes launches but before starting Stub Provider (RJS-1180).

[sync-by-unito]

➤ Franck Franck commented:

Blocking on RJS-1367. This PR seems to more often exercise the code path that triggers segfaults in the Mixed implementation.