Media: Remove documentation detailing specific edge cases in the `image_editor_output_format` filter.

In [51422], a few specific edge cases were detailed so that developers using the hook were aware of known pitfalls.

These edge cases have been fixed in 5.8.1 through [51653] and [51704], so the documentation is no longer necessary.

Props azaozz, audrasjb.
Fixes #53955.
Built from https://develop.svn.wordpress.org/trunk@51717


git-svn-id: http://core.svn.wordpress.org/trunk@51323 1a063a9b-81f0-0310-95a4-ce76da25c4cd

wp-includes/class-wp-image-editor.php

@@ -351,19 +351,6 @@ abstract class WP_Image_Editor {
 		 * Enables filtering the mime type used to save images. By default,
 		 * the mapping array is empty, so the mime type matches the source image.
 		 *
-		 * This should be considered experimental as there are a few edge cases that
-		 * still need to be solved.
-		 *
-		 * When this filter is used in combination with the {@see 'wp_editor_set_quality'}
-		 * filter, the image quality value used will be that of the original mime type,
-		 * not the mapped one. This could result in unexpected image quality for generated
-		 * images. See https://core.trac.wordpress.org/ticket/53667 for more details.
-		 *
-		 * When a mime type is mapped to another, and two images with the same name are
-		 * uploaded (image.jpg and image.webp, for example), the generated images for one
-		 * will potentially overwrite the other's.
-		 * See https://core.trac.wordpress.org/ticket/53668 for more details.
-		 *
 		 * @see WP_Image_Editor::get_output_format()
 		 *
 		 * @since 5.8.0

wp-includes/version.php

@@ -13,7 +13,7 @@
  *
  * @global string $wp_version
  */
-$wp_version = '5.9-alpha-51716';
+$wp_version = '5.9-alpha-51717';
 
 /**
  * Holds the WordPress DB revision, increments when changes are made to the WordPress DB schema.