Contributing a text editor provider raises warning, even when user selects it as 'workbench.editor.defaultBinaryEditor'

Contributing a 'CustomTextEditorProvider', to be selected by the user as 'workbench.editor.defaultBinaryEditor' still raises the warning of 'File seems to be binary and cannot be opened as text'

Context: We are currently developing a VSCode extension, to parse binaries with objdump and provide the information about the binary. We need the output to be presented in a text editor, not a custom editor as we are contributing a new language model for objdump output. So, mainly we need the output syntax coloring, as document symbols to be provided, which is not possible in the custom editor WebView.

We need a way to bypass the warning, as the user selects the provided custom text editor as the default binary editor.

Related Discussion