[gnome-builder/wip/gtk4-port: 641/736] plugins/valgrind: make valgrind plugin load

[Christian Hergert <chergert src gnome org>]

commit 58eac6e5e63e5362ca300904c1a7b433c5b1a091
Author: Christian Hergert <chergert redhat com>
Date:   Tue Apr 19 13:36:59 2022 -0700

    plugins/valgrind: make valgrind plugin load
    
    Now that this is provided internally, we need to actually include the
    valgrind.plugin as part of the resource and ensure menu sections line
    up with what is expected now.

 src/plugins/valgrind/gtk/menus.ui | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
---
diff --git a/src/plugins/valgrind/gtk/menus.ui b/src/plugins/valgrind/gtk/menus.ui
index 4a2e8122a..971e6d527 100644
--- a/src/plugins/valgrind/gtk/menus.ui
+++ b/src/plugins/valgrind/gtk/menus.ui
@@ -1,15 +1,15 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <interface>
   <menu id="run-menu">
-    <section id="run-menu-section">
+    <section id="run-menu-observation-section">
       <item>
         <attribute name="id">valgrind-run-handler</attribute>
         <attribute name="after">default-run-handler</attribute>
         <attribute name="action">run-manager.run-with-handler</attribute>
-        <attribute name="target">valgrind</attribute>
+        <attribute name="target" type="s">'valgrind'</attribute>
         <attribute name="label" translatable="yes">Run with Valgrind</attribute>
         <attribute name="verb-icon-name">system-run-symbolic</attribute>
-        <attribute name="accel">&lt;Control&gt;F10</attribute>
+        <attribute name="accel">&lt;Primary&gt;F10</attribute>
       </item>
     </section>
   </menu>