Project Portal API: Optimize models and data fetching to reduce only necessary fields

[kjetilhau]

Expected outcome

Fusion core's Application management 2.0 is well on the way wee need to migrate to the new service.

https://fusion-s-apps-ci.azurewebsites.net/swagger/index.html
https://fusion-s-apps-test.azurewebsites.net/swagger/index.html
https://fusion-s-apps-fprd.azurewebsites.net/swagger/index.html

All models need to be aligned with the new API service.

Maybe this issue should be handled as a tracker for the whole migration.
Changes needs to me made on all our api's and frontend.

• Backend
• Web Client
• Web Server

Business Value / Developer Experience

User Acceptance Tests (UAT)

Environments

All testing of issues are done in project-portal-test

• project-portal-prod
• project-portal-test
• project-portal-feature

For Backend use these

• project-portal-api-prod
• project-portal-api-test
• project-portal-api-feature

Work to be done

• Optimize models and data fetching to reduce only necessary fields
• Look over and remove unused API endpoints and proxies
• Verify which endpoints that are used in ClientBackend vs. API