Fix: Update document tool to generate a new id after update

[razertory]

Issue：

This project's artifact will have an editing feature, but the newly edited results will overwrite historical artifacts. For example, when Python code V1 is output and I prompt a modification to produce V2, clicking on V1's code displays V2 instead. This differs from projects like v0.dev, which allow viewing rendered content of different artifact versions.

Furthermore, I discovered that the primary key in the Document table of the database is not unique. In the earlier example, querying the database reveals two records with identical IDs—a result that is often confusing and meaningless.

Solution:

At the onUpdate stage, generate a new UUID and save it as a new version.

[vercel]

@razertory is attempting to deploy a commit to the Vercel Team on Vercel.

A member of the Team first needs to authorize it.