LibGfx: Re-structure the whole initialization pattern for image decoders

When trying to figure out the correct implementation, we now have a very
strong distinction on plugins that are well suited for sniffing, and
plugins that need a MIME type to be chosen.

Instead of having multiple calls to non-static virtual sniff methods for
each Image decoding plugin, we have 2 static methods for each
implementation:
1. The sniff method, which in contrast to the old method, gets a
    ReadonlyBytes parameter and ensures we can figure out the result
    with zero heap allocations for most implementations.
2. The create method, which just creates a new instance so we don't
    expose the constructor to everyone anymore.

In addition to that, we have a new virtual method called initialize,
which has a per-implementation initialization pattern to actually ensure
each implementation can construct a decoder object, and then have a
correct context being applied to it for the actual decoding.

Userland/Libraries/LibGfx/JPGLoader.cpp

@@ -1179,12 +1179,22 @@ bool JPGImageDecoderPlugin::set_nonvolatile(bool& was_purged)
     return m_context->bitmap->set_nonvolatile(was_purged);
 }
 
-bool JPGImageDecoderPlugin::sniff()
+bool JPGImageDecoderPlugin::initialize()
 {
-    return m_context->data_size > 3
-        && m_context->data[0] == 0xFF
-        && m_context->data[1] == 0xD8
-        && m_context->data[2] == 0xFF;
+    return true;
+}
+
+ErrorOr<bool> JPGImageDecoderPlugin::sniff(ReadonlyBytes data)
+{
+    return data.size() > 3
+        && data.data()[0] == 0xFF
+        && data.data()[1] == 0xD8
+        && data.data()[2] == 0xFF;
+}
+
+ErrorOr<NonnullOwnPtr<ImageDecoderPlugin>> JPGImageDecoderPlugin::create(ReadonlyBytes data)
+{
+    return adopt_nonnull_own_or_enomem(new (nothrow) JPGImageDecoderPlugin(data.data(), data.size()));
 }
 
 bool JPGImageDecoderPlugin::is_animated()