Update verzoek plugin to not use attachments

[Niek-Ritense]

Why

Why do we need this feature?

• Problem Statement: Currently, documents in the "verzoek" plugin are placed within an "attachments" array, which limits control over how these documents are managed and accessed. This setup creates challenges for users who need more tailored handling of documents for various workflows and integrations.
• Value Proposition: By allowing documents to be managed independently of the attachments array, users will gain greater flexibility in handling documents according to specific requirements. This change will enhance document management functionality within the plugin, making the user experience more intuitive and aligned with the users’ needs for customization.

How

How do we envision this feature working?

• Guiding Principles: This feature should give the implementation flexibility and control over document management.
• Key Use Cases:
• Custom Document Management: Users can store, retrieve, and organize documents independently rather than being confined to an attachments array.
• Customer title naming dependency: You are no longer dependent on the right naming of the customer for the documents
• Improved Integration: Allows easier integration with external document management systems or internal workflows needing specific document handling.

What

What needs to be done to implement this feature?

• Feature Description: Update the verzoek plugin to provide a separate structure for documents, allowing them to be managed outside the attachments array. This includes creating or updating APIs, database structures, and front-end interfaces to support independent document management.
• Requirements:
• Modify the current plugin structure to support independent document management.
• update bpmn of create zaakdossier
• handle all documents to be linked to open zaak
• Acceptance Criteria:
• Documents are managed independently from the attachments array.
• Documents are all liked to open zaak
• The implenentation can pick the locations where the documents are and give the right title to it

Additional Context

• Stakeholders: all users of the verzoek plugin and open forms
• References: GitHub Issue #4689 for additional context and discussion.
• Potential Challenges:
• Potential complexity in separating document management from existing attachment workflows.
• needing to update the common ground verzoek standaard

---