Put application tables in schema

[Ceredron]

Description

It's best practice to put the tables that belong to our application in its own schema (namespacing). It also makes managing access easier.

We also ensure that both developers and the application has access to Hangfire tables. This is necessary if/when we need to troubleshoot. This also enables us to create a separate Hangfire dashboard application if we see that it is needed.
We can also enable Hangfire dashboard in our main app, but our main app will be blocked from the open internet and ingress will only be allowed through APIM. In theory it should be possible to configure APIM such that it can be used with Hangfire dashboard. But I think it would be harder (especially when we add OIDC login with its re-directs to it).

After this is merged all developers need to wipe their local database. (Delete docker database container, re-run "docker-compose up -d".)

Related Issue(s)

• Schema for correspondence-tabeller #193

Verification

• Your code builds clean without any errors or warnings
• Manual testing done (required)
• Relevant automated test added (if you find this hard, leave it and we'll help out)
• All tests run green

Documentation

• User documentation is updated with a separate linked PR in altinn-studio-docs. (if applicable)

[Andreass2]

When creating new migrations from console, does it use the correct schema automaticly?

[Andreass2]

Looks good.

Also nice to improve naming of azure resources.

[Ceredron]

When creating new migrations from console, does it use the correct schema automaticly?

Yeah (tested to be safe😅)
It's because of:
modelBuilder.HasDefaultSchema("correspondence");
So all tables created through our DbContext ends up in the correspondence schema.