Document metabase optional configuration (email, ...) (#1136)

Steps are as of now manual. Once we have more usage and traction of
metabase we may consider automating these steps via Metabase API.

Email to be used is the same as for support. Once we see need, we can
create separate email for metabase.

Related Issue/s:
* #1114

Author: YuryHrytsuk

services/metabase/README.md

@@ -6,3 +6,20 @@ Before deploying metabase first time, make sure that postgres is configured:
     * you can get one via adminer or by directly connecting to container and executing `psql -U <user> -d <db>`
 
 This can be automated via https://github.com/ITISFoundation/osparc-ops-environments/issues/827
+
+## Extra Configuration (optional)
+
+Setting up email (manual):
+* go to admin settings
+* go to email
+* configure email using SMTP_HOST, SMTP_PASSWORD, SMTP_PORT, SMTP_PROTOCOL, SMTP_USERNAME env from config
+  - Note: `FROM NAME` shall potentially clearly indicate deployment (if we use metabase in multiple deployments this helps to avoid confusion)
+  - Note: `FROM ADDRESS` use support email (we may consider adding a separate user and mail for metabase later)
+  - Note: `REPLY-TO ADDRESS` must NOT be support email. Feel free to choose some of backenders / devops email
+
+Configuring localization (manual):
+* go to admin settings
+* go to localization
+* configure first day of the week to be `Monday`
+
+Note: later these manual steps can be automated via Metabase API calls