Add support for cases where there are multiple stakeholders before deleting instances with DataCleanup

[SandGrainOne]

Description

The confirm endpoint can store confirmations from many stakeholders. Like if there are more than one application owner that is supposed to download instances for an App. What we don't have is any way of supporting this in DataCleanup. The job will delete instances confirmed by the application owner. It will not wait for confirmation from any other stakeholders. Mostly because it has no way of knowing.

We need a new property on application metadata that can tell the Cleanup job that it should wait for confirmation from multiple stakeholders. There are information about this in policy.xml, but I'm not sure if access to instances should automatically mean wait for confirmation.

Considerations

Describe input (beyond tasks) on how the user story should be solved can be put here.

Acceptance criteria

Describe criteria here (i.e. What is allowed/not allowed (negative tesing), validations, error messages and warnings etc.)

Specification tasks

• [ ] Development tasks are defined
• [ ] Test design / decide test need

Development tasks

Add tasks here

Definition of done

Verify that this issue meets DoD (Only for project members) before closing.

• [ ] Documentation is updated (if relevant)
  • [ ] Technical documentation (docs.altinn.studio)
  • [ ] User documentation (altinn.github.io/docs)
• [ ] QA
• [ ] Manual test is complete (if relevant)
• [ ] Automated test is implemented (if relevant)
• [ ] All tasks in this userstory are closed (i.e. remaining tasks are moved to other user stories or marked obsolete)

[FinnurO]

Related to #4274