Feature Request: In addition to "Grant" and "Reject", provide "Return" to send the request back to the user

Overview of the Feature Request
In addition to "Grant" and "Reject" for access requests, provide the option to "Return" the request to the user, preferably with functionality with a note or message where the approver evaluating the request can tell the applicant why it has been returned.

The applicant can then get their original request, modify their responses accordingly and resubmit. This can go back and forth as many times as necessary. When it is finally approved, the final guestbook responses recorded in the dataverse database reflect the actual approved request.

What kind of user is the feature intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)

Approver - click a "Return" to user button, add comment as to what the problem is.
Applicant - be able to resubmit an updated guestbook response.

Likely API endpoints are required too.

What inspired the request?

This is aimed at "Request at Access Request" functionality, where an applicant submits their request and their guestbook responses are evaluated before the decision to accept or reject the application is made and actioned.

In the ADA use case, the Approvers often have to return the application to the user and ask them to provide further information, or to correct information in their application. This back and forth between ADA and the applicant all happens in a ticketing system, after a ticket is created with the original access request with the gb responses. As there is currently no way to update the original guestbook responses, the gb responses recorded in the database when the request is finally approved do not reflect the final agreed upon details as recorded in the ticketing system.

ADA has to extract all the information reflecting the final responses from the ticket(s) which creates a lot of extra work for the data owners. And the db gb responses are different from the final (ticket) approved responses.

What existing behavior do you want changed?

None

Any brand new behavior do you want to add to Dataverse?

As described above

Any open or closed issues related to this feature request?

Not sure.

Are you thinking about creating a pull request for this feature?
Help is always welcome, is this feature something you or your organization plan to implement?

ADA does not have the resources to contribute code.

The issue names no files, tests, or entry points; start by tracing the access-request approval, guestbook-response, and API flows. Done would include a return state with an approver note, applicant editing and resubmission, and final approved responses reflecting the latest submission, with the required API behavior covered.