play: Initialize debug category and error quark in class_init

Doing it in gst_play_new() means that bindings that directly call g_object_new() with the GType wouldn't end up initializing both. This affects at least the Python and GJS bindings.

gst_init() is nonetheless only called from gst_play_new() once because calling it from class_init would likely lead to problems as that's called from somewhere in the middle of GObject.

added 1.22 1.24 Needs backport labels

added Merge in 5 days label

Marking as "merge in 5 days"

removed Merge in 5 days label

assigned to @gstreamer-merge-bot

mentioned in commit slomo/gstreamer@7c871ec2

mentioned in commit slomo/gstreamer@c2ced1c0

added 39 commits

• e83530ec...19bc0da8 - 37 commits from branch gstreamer:main
• 7c871ec2 - play: Initialize debug category and error quark in class_init
• c2ced1c0 - play: Mention that gst_play_new() also initialized GStreamer

Compare with previous version

assigned to @slomo and unassigned @gstreamer-merge-bot

I couldn't merge this branch: CI failed! See pipeline https://gitlab.freedesktop.org/slomo/gstreamer/-/pipelines/1173442.

added 2 commits

• c9b4c30a - play: Initialize debug category and error quark in class_init
• 7a414cf7 - play: Mention that gst_play_new() also initialized GStreamer

Compare with previous version

assigned to @gstreamer-merge-bot and unassigned @slomo

mentioned in commit slomo/gstreamer@fcd7807d

mentioned in commit slomo/gstreamer@e049013d

added 39 commits

• 7a414cf7...19bc0da8 - 37 commits from branch gstreamer:main
• fcd7807d - play: Initialize debug category and error quark in class_init
• e049013d - play: Mention that gst_play_new() also initialized GStreamer

Compare with previous version

merged

changed milestone to %1.25.1

mentioned in commit gstreamer-backport-bot/gstreamer@582723a7

mentioned in commit gstreamer-backport-bot/gstreamer@5f3f5fd1

added Backported into 1.24 label