Rename EE markdown_processing_spec

This way, when the user runs `yarn run jest spec/frontend/content_editor/markdown_processing_spec`
it won't run both the EE and CE spec. This fixes some confusion when
using the `FOCUSED_MARKDOWN_EXAMPLES` environment variable.

spec/fixtures/markdown/markdown_golden_master_examples.yml

@@ -8,7 +8,7 @@
 # For EE, these files are used:
 # EE Data:     ee/spec/fixtures/markdown/markdown_golden_master_examples.yml
 # EE Backend:  ee/spec/requests/api/markdown_golden_master_spec.rb
-# EE Frontend: ee/spec/frontend/content_editor/markdown_processing_spec.js
+# EE Frontend: ee/spec/frontend/content_editor/ee_markdown_processing_spec.js
 #
 #
 # Requirements:

spec/frontend/content_editor/markdown_processing_spec_helper.js

@@ -67,16 +67,6 @@ const testSerializesHtmlToMarkdownForElement = async ({ markdown, html }) => {
 export const describeMarkdownProcessing = (description, markdownYamlPath) => {
   const examples = loadMarkdownApiExamples(markdownYamlPath);
 
-  // If examples were filtered out, we need to create at least one dummy test
-  // so Jest doesn't blow up.
-  if (!examples.length) {
-    describe(description, () => {
-      // eslint-disable-next-line jest/no-disabled-tests
-      it.skip('skipped because no examples matched filter', () => {});
-    });
-    return;
-  }
-
   describe(description, () => {
     describe.each(examples)('%s', (name, { pendingReason, ...example }) => {
       const exampleName = 'correctly serializes HTML to markdown';