Description Of Changes

Update clients to support uploading multiple attachments instead of just one, when completing a manual task from

Code Changes

• Update types
• Removed max count for Ant Upload files
• Update both CompleteModals and both manual task slices (admin-ui and external-task ui in privacy center) to support multiple attachments
• Added a cypress test, updated the other ones

Steps to Confirm

1. Setup an Manual Task integration with multiple file task fields and assign it to an external user
2. Go to Request Manager and create a new request
3. Approve the new request
4. Go to manual task and solve one of the file tasks uploading multiple files
5. Login in the external task portal and complete another file task uploading multiple files
6. Back in admin-ui, go to that last privacy request and check that in the Activity view it shows the completed task and it shows "2 attachments", the tooltip should should the filenames for the 2 attachments submitted.

Pre-Merge Checklist

• Issue requirements met
• All CI pipelines succeeded
• CHANGELOG.md updated
  • Add a db-migration This indicates that a change includes a database migration label to the entry if your change includes a DB migration
  • Add a high-risk This issue suggests changes that have a high-probability of breaking existing code label to the entry if your change includes a high-risk change (i.e. potential for performance impact or unexpected regression) that should be flagged
  • Updates unreleased work already in Changelog, no new entry necessary
• Followup issues:
  • Followup issues created
  • No followup issues
• Database migrations:
  • Ensure that your downrev is up to date with the latest revision on main
  • Ensure that your downgrade() migration is correct and works
    • If a downgrade migration is not possible for this change, please call this out in the PR description!
  • No migrations
• Documentation:
  • Documentation complete, PR opened in fidesdocs
  • Documentation issue created in fidesdocs
  • If there are any new client scopes created as part of the pull request, remember to update public-facing documentation that references our scope registry
  • No documentation updates required