[Question][Feature Request] Add ability to go from standalone editor into a diff editor

Context

• This issue is not a bug report. (please use a different template for reporting a bug)
• This issue is not a duplicate of an existing issue. (please use the search to find existing issues)

Description

We use Monaco IStandaloneCodeEditor in our app and we want to incorporate a copilot feature with similar experience of GitHub Copilot.

Question1: Based on this issue from 4 years ago, if we start with IStandaloneCodeEditor in normal editing mode, and then replace it with IStandaloneDiffEditor when users trigger the copilot in our app, it involves destroying the DOM elements for IStandaloneCodeEditor and then create a new IStandaloneDiffEditor. Is this correct, and is there an easier way to implement this in monaco?

Question2: This might be a vague question, I wonder do all the features supported by IStandaloneCodeEditor also supported by IStandaloneDiffEditor? I'm asking this because I want to understand if there's any known limitation on IStandaloneDiffEditor before I go ahead and change everything of our editor to a IStandaloneDiffEditor and then realize there are certain features we are gonna lose.

Question3: If we have the bandwidth to contribute to your repo, is there an underlying reason that stops a IStandaloneDiffEditor to be built on top of a IStandaloneCodeEditor? We would like to learn about, if it's possible to make the transition easier, and we are glad to help if it's something feasible.

Monaco Editor Playground Link

N/A

Monaco Editor Playground Code

N/A

The request centers on IStandaloneCodeEditor and IStandaloneDiffEditor; start by reviewing their APIs and the linked issue #1881. Done would require a decided transition path, a clear answer about feature parity, or an agreed contribution scope.