[ADD] mail_client_extension

[Florimond]

This module provide routes to manage people, companies, and
leads from the outlook add-on, but could eventually be accessed by
add-ons for other mail clients.

Task ID: 2128295

[Florimond]

@odony
So crm_addons/controllers/main.py:_authorize(request) is called at the beginning of every controller method.
See also web_login and exchange_with_token. In the latter, I kept the JWT generation even though it's not something useful for outlook. According to @qmo-odoo it's going to be useful for the gmail addon.

So basically the flow is as follow:

1. Browser opens a dialog showing the odoo login page (/crm/addons/login), passing in the url a redirect url that redirects to the outlook addon (the react web app).
2. The user enters its credentials on the login page.
3. The credentials are POSTED by the browser to /crm/addons/login
4. /crm/addons/login sends back a redirect to https://myReactApp/?success=1&response_type=code&code=THE_CODE
5. The browser does the redirect to the react app
6. The react app does a POST to exchange that token received in URL

You'll find the code of the outlook "add in" under web_outlook.

[Florimond]

@odony Any comment about this?

[mart-e]

first review, will continue later

[xmo-odoo]

It's a React web app.

Why?

[awa-odoo]

Hello @Florimond

When you have some time, there are still some interesting comments on the PR from XMO and MAT that are left unanswered.

Also, may I ask you to rework the PR like the following:

• One commit with the "Odoo" code, models/controllers/...
• One commit with all the Outlook specific code (basically the React stuff)
• One commit only for the package.lock (if possible, because it ruins the diff a little)

That will allow me to review everything more easily.

Thank you :)

Side note: the code is conflicting with master so you might want to rebase too.

[xmo-odoo]

@robodoo r+