Make column names consistent

[Ceredron]

Description

If we use _pk and _fk suffixes, we should do so consistently.

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]

Following should also be changed:
altinn_resource.service_owner_id -> altinn_resource.service_owner_id_fk
party.organization_number -> party.organization_number_pk

[Ceredron]

Following should also be changed: altinn_resource.service_owner_id -> altinn_resource.service_owner_id_fk party.organization_number -> party.organization_number_pk

Good catch!
I fixed this, and also re-wrote some of the sql queries to not use "SELECT *", but instead specifying columns. It's not super-important, but usually considered best practice.
https://bornsql.ca/blog/why-you-should-not-use-select/
Main reason is that the optimizer/planner may not work as intended some times.

[tomshag]

Looks good.