feat: Catalog version in footer for Login, Dasboard and Detail pages

[boris-bc]

Description

This change adds version number to the Login, Dashboard and Detail pages. The version number is taken from the gradle.properties and is populated into .env, from where it is displayed in the pages. The changes also contain a little bit of code cleanup removing some of the API portal specific code that is no longer used from this repo.

Linked to #3332

Type of change

• fix: Bug fix (non-breaking change which fixes an issue)
• feat: New feature (non-breaking change which adds functionality)
• docs: Change in a documentation
• refactor: Refactor the code
• chore: Chore, repository cleanup, updates the dependencies.
• BREAKING CHANGE or !: Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• My code follows the style guidelines of this project
• PR title conforms to commit message guideline ## Commit Message Structure Guideline
• I have commented my code, particularly in hard-to-understand areas. In JS I did provide JSDoc
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• The java tests in the area I was working on leverage @nested annotations
• Any dependent changes have been merged and published in downstream modules

[taban03]

maybe we can have an e2e (cypress) test to check that the label is visible

[boris-bc]

maybe we can have an e2e (cypress) test to check that the label is visible

Tests added.

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarCloud

[balhar-jakub]

This looks really good. Thanks for the change.