🎨 [Frontend] Make version display more prominent

[odeimaiz]

What do these changes do?

• In the version selector, only the versionDisplay is visible
• In the Service Large card, version will be either versionDisplay or version. For testers, the integration version will show the version.

Bonus:

• Version selector as wide as the widest list item
• Fix min Visible Inputs, metadata key changed
• Cache service resources

Related issue/s

related to ITISFoundation/osparc-issues#1404

How to test

Dev-ops checklist

• No ENV changes or I properly updated ENV (read the instruction)

[elisabettai]

Thanks! Some questions (I may be out of date on how this has evolved in the past 2 weeks, so happy to have a look together in person).

1. From a regular user point of view: what happens to the version selector if a "version display" in not specified? How can they choose an older version of a service?
2. Similarly to 1, what will the service selector show when they open the service catalog in the workbench?
   

[odeimaiz]

Thanks! Some questions (I may be out of date on how this has evolved in the past 2 weeks, so happy to have a look together in person).

1. From a regular user point of view: what happens to the version selector if a "version display" in not specified? How can they choose an older version of a service?
2. Similarly to 1, what will the service selector show when they open the service catalog in the workbench?
   

From this PR on, where we show the version number, if there is a displayVersion available, this is what it will be shown.

[elisabettai]

Thanks! Some questions (I may be out of date on how this has evolved in the past 2 weeks, so happy to have a look together in person).

1. From a regular user point of view: what happens to the version selector if a "version display" in not specified? How can they choose an older version of a service?
2. Similarly to 1, what will the service selector show when they open the service catalog in the workbench?
   

From this PR on, where we show the version number, if there is a displayVersion available, this is what it will be shown.

Ok, thanks! So for old-school services (without versionDisplay), everything will behave as before if I understand it well.

[odeimaiz]

Thanks! Some questions (I may be out of date on how this has evolved in the past 2 weeks, so happy to have a look together in person).

1. From a regular user point of view: what happens to the version selector if a "version display" in not specified? How can they choose an older version of a service?
2. Similarly to 1, what will the service selector show when they open the service catalog in the workbench?
   

From this PR on, where we show the version number, if there is a displayVersion available, this is what it will be shown.

Ok, thanks! So for old-school services (without versionDisplay), everything will behave as before if I understand it well.

correct

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud