Homogenize studies and services

[odeimaiz]

What do these changes do?

This PR brings templates closer to services.

The "Services" tab was renamed to "Discover". Under this tab, we list all the available resources (templates and services) to start a new study:

• If a templates is selected, a study containing that pipeline will be initialized (same as before)
• If a service is selected, a study containing that single node will be initialized (new feature). Since this will be a single node study, the service/app will be automatically maximized. Providing a more app-like user experience.

The Studies tab now shows only the studies the logged in user has access to. This list could also be spitted into different sections, such as, "Owned by me", "Shared with me", "Shared with my organizations"...

In addition, the content of the Discover tab is also shipped by the frontend compiler with its own customized navigation bar as standalone application that could be served as the Discover/Explore website.

Bonus:

• Clean up:
  • Plotly is not used
  • Removed unused images

Related issue number

related to ITISFoundation/osparc-issues#68

How to test

Checklist

• Did you change any service's API? Then make sure to bundle document and upgrade version (make openapi-specs, git commit ... and then make version-*)
• Unit tests for the changes exist
• Runs in the swarm
• Documentation reflects the changes
• New module? Add your github username to .github/CODEOWNERS

[codecov]

Codecov Report

Merging #1569 into master will increase coverage by 12.2%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master   #1569      +/-   ##
=========================================
+ Coverage    61.4%   73.7%   +12.2%     
=========================================
  Files         278     278              
  Lines       10874   10874              
  Branches     1181    1181              
=========================================
+ Hits         6687    8015    +1328     
+ Misses       3875    2516    -1359     
- Partials      312     343      +31     

Flag	Coverage Δ
#integrationtests	56.6% <ø> (ø)
#unittests	67.3% <ø> (+6.4%)	⬆️

Impacted Files	Coverage Δ
.../director/src/simcore_service_director/producer.py	63.0% <0.0%> (-0.5%)	⬇️
.../web/server/src/simcore_service_webserver/utils.py	43.1% <0.0%> (+2.2%)	⬆️
...imcore_service_webserver/resource_manager/redis.py	93.7% <0.0%> (+6.2%)	⬆️
...er/src/simcore_service_webserver/login/__init__.py	93.1% <0.0%> (+6.8%)	⬆️
...rc/simcore_service_webserver/application_config.py	100.0% <0.0%> (+7.4%)	⬆️
.../server/src/simcore_service_webserver/login/cfg.py	78.9% <0.0%> (+7.8%)	⬆️
...s/web/server/src/simcore_service_webserver/rest.py	89.5% <0.0%> (+8.3%)	⬆️
...er/src/simcore_service_webserver/catalog_config.py	91.6% <0.0%> (+8.3%)	⬆️
...rver/src/simcore_service_webserver/security_api.py	75.8% <0.0%> (+10.3%)	⬆️
...erver/src/simcore_service_webserver/login/utils.py	52.8% <0.0%> (+11.2%)	⬆️
... and 58 more

[ignapas]

IMHO, the whole thing a bit confusing. We have studies which are composed by services... and then we can group services to form new studies... but there is a clear separation between services and studies. With these apps, what we do is to create a study that contains only one service, but I don't think that is clear enough for the user. Sorry, I probably missed the discussion about this.
I couldn't test it with a full list of studies as I had trouble migrating the database. What I could test and the code looks good.
MINOR: We you create several studies from the same service, study names duplicate.

[ignapas]

the server sends json as plain text? it could probably send it as application/json and then retrieve it client side directly as an object.
if this is not possible, it could be nice to wrap the parsing of the json, and add a try, as JSON.parse can also fail