fix: destroy when using forms and display fields API

[Paul-Bob]

Description

Fixes #2403

The detach button request has been updated to no longer hydrate the resource using the destroy view, as it was identified as a problematic approach when using def display_fields or def form_fields API since those methods wouldn't get called.

To address this, we have modified the process to include passing the current view as parameters during the detach request. This ensures that the appropriate view is properly hydrated into the resource.

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works

Screenshots & recording

Before

before.webm

After

after.webm

Manual review steps

1. Set a resource with an association field using only def display_fields and def form_fields API
2. Visit resource's show view
3. Detach a record from the association field
4. Before was raising error, notice that now it works.

[codeclimate]

Code Climate has analyzed commit 9590f39 and detected 0 issues on this pull request.

View more on Code Climate.

[Paul-Bob]

This logic avoid the following scenario:

When a has many field is rendered the action is index and params[:view] is show or edit but we want to keep @view as index for the related_resource

Same do not happen with other actions except the list on L126

[adrianthedev]

Please add this as a comment in the code so we know why it's there.

[adrianthedev]

Please add this as a comment in the code so we know why it's there.

[github-actions]

This PR has been merged into main. The functionality will be available in the next release.

Please check the release guide for more information.