not dirty if auto-save soon without any save error state

[amunger]

fixes #140069

[amunger]

cc @bpasero

[bpasero]

@amunger fyi stored file working copies know if they are in error state from saving or not, see:

vscode/src/vs/workbench/services/workingCopy/common/storedFileWorkingCopy.ts

Lines 134 to 140 in ee5d95e

	/**
	* Whether the stored file working copy is in the provided `state`
	* or not.
	*
	* @param state the `FileWorkingCopyState` to check on.
	*/
	hasState(state: StoredFileWorkingCopyState): boolean;

[amunger]

@amunger fyi stored file working copies know if they are in error state from saving or not, see:

ah, thanks. That makes things simpler. I can also include conflict state in the same way, though I never figured if that would apply to notebooks.

[bpasero]

@amunger conflict state is also an error state, so I think you are fine:

vscode/src/vs/workbench/services/workingCopy/common/storedFileWorkingCopy.ts

Lines 1068 to 1074 in 1e0b12d

	// Flag as error state
	this.inErrorMode = true;
	// Look out for a save conflict
	if ((error as FileOperationError).fileOperationResult === FileOperationResult.FILE_MODIFIED_SINCE) {
	this.inConflictMode = true;
	}

[bpasero]

@amunger fyi this is not needed, you already pass the this._workingCopyListeners in

[amunger]

thanks, I was wondering about that. It stands out as the only listener that was disposed that way in this method