Add support for the upcoming user info API

[teolemon]

Description

Add support for the upcoming user info API
openfoodfacts/openfoodfacts-server#9918

[stephanegigandet]

Note that we are planning to remove the email from the body. Is it needed for the app? cc @monsieurtanuki @g123k

[monsieurtanuki]

Note that we are planning to remove the email from the body. Is it needed for the app? cc @monsieurtanuki @g123k

@stephanegigandet In Smoothie we don't need the user email field returned by /cgi/auth.pl:

• we only use /cgi/auth.pl once, in off-dart's method login2
• we only use method login2 once, in Smoothie's method getLoginResult
• inside method getLoginResult, we only extract the user_id field

In Smoothie the user may log in with the user id or the email (same password).

Actually, from openfoodfacts/smooth-app#2464 openfoodfacts/smooth-app#3499 we explicitly use the returned user_id field instead of whatever the user typed in (user id or email) because it created side-effects to use user email.

Possible confusion: is the returned user_id always a "decent" user id - and never an email?

[stephanegigandet]

@monsieurtanuki Perfect, thanks for checking, I will remove the email field.
The returned user_id is always the user id, never an email

[M123-dev]

Is the full endpoint documented somewhere