Allow plugin updates that break existing code after explicit confirmation

When a project's plugin selection changes, Studio deliberately recompiles the project and refuses the change if it would introduce new compile errors, so an update can never silently break existing code. However, when a new plugin version intentionally renames or removes members, there is no way to proceed: the add/update flow reports the compile errors in a status message (or disables the Add button during import) and the only workaround is to comment out every reference in the Objo code, apply the plugin change, then uncomment and repair the code. Nothing explains this or offers an explicit override, even though the underlying conflict exception was designed to support one.

Removing a plugin reference already handles this correctly: it shows the affected project, lists what would break, and offers "Remove it anyway?" before retrying with the waiver. Adding and updating a plugin should offer the same explicit path.