feat(assets): add reassociate, disassociate, and delete actions

[TylerAdamMartinez]

Why

This PR addresses the following problem/context:

• Adds the ability to manage well attachments directly from the attachment preview.

How

Implementation summary - the following was changed/added/removed:

• Added attachment management actions (Disassociate, Reassociate, Delete) behind a contextual actions menu.
• Added confirmation dialogs for destructive operations.
• Added a reassociation dialog with searchable well selection using autocomplete.
• Integrated asset mutation endpoints for reassociation, disassociation, and deletion.
• Added success and error notifications for attachment management actions.

Notes

Any special considerations, workarounds, or follow-up work to note?

• Attachment management controls are only available for users with the appropriate management permissions.

[github-actions]

Preview Deployment

Preview URL: https://preview-feature-tam-bdms-922-auejgdbofq-uc.a.run.app

Note: This preview uses the staging API endpoints.

[TylerAdamMartinez]

@lizalino, this PR also allows the user to delete the underlying asset. I noticed that a DELETE asset endpoint exists while working on the backend for this task. If you want me to remove that feature, just let me know. Also, the ability to see a list of all unassociated assets and reassign them, if the user wishes, will be in a future PR.

[chasetmartin]

@TylerAdamMartinez Just a heads up I tried the delete asset - and it worked as expected. I saw in the Slack activity-log my upload action, but I didn't see the delete action in the activity-log when I deleted the asset. It looks like the notify_edit_event function in the API only fires when user is passed in model_deleter, and it is not currently.

I think that would be an easy fix in order to track any delete actions in the log (if delete is kept).

[TylerAdamMartinez]

@TylerAdamMartinez Just a heads up I tried the delete asset - and it worked as expected. I saw in the Slack activity-log my upload action, but I didn't see the delete action in the activity-log when I deleted the asset. It looks like the notify_edit_event function in the API only fires when user is passed in model_deleter, and it is not currently.

I think that would be an easy fix in order to track any delete actions in the log (if delete is kept).

Create this PR to resolve this issue: PR#742