feature: webserver: fusion apps service migration

[kjetilhau]

Description

Migrate the proxy in webserver to the new Fusion Apps API service.

• PR title and description are to the point and understandable
• I have performed a self-review of my own code'

Please select version type the purposed change:

• major
• minor
• patch
• none

External Relations

• database migration

Changeset

• BREAKING CHANGE: The previous proxy endpoint: /bundles/apps/{appKey}/resources/{*resourcePath} is no more. Instead use /fusion-apps/{*wildcard*} to make proxy calls against the whole Fusion Apps API. See Fusion Apps API Swagger documentation for more information about routes.
• Migrated proxy from Fusion Portal to Fusion Apps API
• Updated packages to latest version
• Refactored and simplified code
• Removed unused Project Portal variables in frontend
• Update frontend to use the new proxy endpoints
• Make frontend client use the new types provided by fusion core
• Update the legacy app loader to use the new proxy endpoints and and fix types
• Move legacy app code to apps folder for cleaner repository
• Setup build of legacy app loader in build pipeline for constant build an deployment.
• Update all Fusion dependencies for frontend client

[changeset-bot]

🦋 Changeset detected

Latest commit: 62bd9c7

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
fusion-project-portal	Major

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[kjetilhau]

@Noggling Let me know if you have any other suggestions for the proxy url path, currently: /fusion-apps/... The important thing is to have a path that does not interfere with the frontend router.