Refactor KRR/OVV to use EF state, not YUNIQL.

[olebhansen]

DB deploy as separate step/user. NOT during application start.

Intent with regards to separate deploy step:

• App-user should not have rights to perform DDL-changes. Hence DB deployment must happen in a separate context/step (workflow or init-container).

Assumption:

• Only 1 DB context for both KRR and OVV.
• DB-first approach (based on EF generated scripts - NB: unique index vs. constraint)

OK to drop everything in the existing DB and start over.

Acceptance criterias:

• YUNIQL removed/not present in in KRR and OVV projects/repo
• DB changes managed and deployed from EF
• User for deploy is not the same as the app-user

---

From identical/duplicate-issue #190

Description

Find out how to set up EF tooling to perform database migration and add a release pipeline step. It's a goal to use the same mechanism to perform database migration for local developlent using Aspire.

Additional information

The altinn-studio team is already doing database migration this way.
https://github.com/Altinn/altinn-studio/blob/main/backend/Migrations.Dockerfile

Tasks

• Add a step to the release pipline for database migration

Acceptance criteria

• Database migration is performed as a step during deployment and not by the Profile application