fix: fix the answer regenerate bug(#15060)

[Jimmy0769]

Summary

Fixes #15060

Tip

Close issue syntax: Fixes #<issue number> or Resolves #<issue number>, see documentation for more details.

Screenshots

Before	After
...	...

Checklist

Important

Please review the checklist below before submitting your pull request.

• This change requires a documentation update, included: Dify Document
• I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!)
• I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change.
• I've updated the documentation accordingly.
• I ran dev/reformat(backend) and cd web && npx lint-staged(frontend) to appease the lint gods

[Jimmy0769]

@weridolin

[laipz8200]

Could you please explain the reason for this change in more detail? I don't think we should be exposing the upload_file_id.

[Jimmy0769]

Could you please explain the reason for this change in more detail? I don't think we should be exposing the upload_file_id.

Because regenerate answer need the upload_file_id, after refresh the chat page, the "message" api will expose the wrong file id, it cause the regenerate error
Before refresh the page:

After refresh the page:

However, I exposed the upload_file_id because I don't know what the id returned by the message api is useful, so I added another field upload_file_id. If the id can be modified to upload_file_id, then the front-end does not need to modify it.