Standardize tier1 in gating

The tier1 tests were traditionally run by BaseOS CI by various
tasks if the baseos-ci.brew-build.* family, typically implemented
by Beaker jobs.

Every component used to have its own special flavor of the
configuration, both in BaseOS CI (the triggering part) and here in
the component's gating.yaml (results processing).

The each-component-is-a-snowflake approach didn't work very well,
creating discrepancies like RHEL-140879.

At long last, I've unified the BaseOS CI configuration for all my
components:
- drop the Beaker job(s) (which have been declared obsoleted anyway)
- trigger two OpenStack jobs
  - "fast lane" for architectures where we usually get results fast,
    sometimes it's advantageous to take a look ASAP
  - "slow lane" for architectures we typically have to wait
For reference, it's commit d2baef686 in baseos-qe/citool-config.

Now I'm fixing the counterpart in gating.yaml (results processing):
We wait for the "fast lane" and "slow lane" results and they both
must pass.

.gcc-toolset-15-annobin.metadata

@@ -1 +0,0 @@
-6d59316779c96fa5e1c0724c907220b2fc3a40ab SOURCES/annobin-12.93.tar.xz

.gitignore

@@ -1 +0,0 @@
-SOURCES/annobin-12.93.tar.xz

annobin-gcc-plugin-ignore-major-version-diffs.patch

@@ -0,0 +1,15 @@
+--- annobin.orig/gcc-plugin/annobin.cc	2024-08-08 12:39:01.928844852 +0100
++++ annobin-12.65/gcc-plugin/annobin.cc	2024-08-08 12:42:07.333437024 +0100
+@@ -3218,9 +3218,10 @@ plugin_init (struct plugin_name_args *
+ 	 be sufficient.  [FIXME: It turns out that this is not entirely true...]  */
+       if (strncmp (version->basever, gcc_version.basever, strchr (version->basever, '.') - version->basever))
+ 	{
+-	  annobin_inform (INFORM_ALWAYS, "Error: plugin built for compiler version (%s) but run with compiler version (%s)",
++	  annobin_inform (INFORM_ALWAYS, "Warning: plugin built for compiler version (%s) but run with compiler version (%s) - disabling",
+ 			  gcc_version.basever, version->basever);
+-	  fail = true;
++	  enabled = false;
++	  return 0;
+ 	}
+ 
+       /* Since the plugin is not part of the gcc project, it is entirely

gating.yaml

@@ -0,0 +1,9 @@
+--- !Policy
+product_versions:
+  - rhel-8
+decision_context: osci_compose_gate
+rules:
+  - !PassingTestCaseRule {test_case_name: baseos-ci.brew-build.gate-build-fast-lane.functional}
+  - !PassingTestCaseRule {test_case_name: baseos-ci.brew-build.gate-build-slow-lane.functional}
+annocheck:
+  - hardened: --skip-property-note --skip-lto --skip-branch-protection --skip-dynamic-tags --ignore-unknown --verbose

plans/ci.fmf

@@ -0,0 +1,5 @@
+summary: CI Gating Plan
+discover:
+    how: fmf
+execute:
+    how: tmt

rpminspect.yaml

@@ -0,0 +1,11 @@
+---
+runpath:
+  allowed_paths:
+    - /usr/lib64
+
+specname:
+    # In GCC toolsets builds, the spec file name and the package are not
+    # exactly the same, the package is prefixed with gcc-toolset-NN-.
+    # Let's ignore the prefix in the specname test.
+    match: suffix
+    primary: filename

sources

@@ -0,0 +1 @@
+SHA512 (annobin-12.93.tar.xz) = d49670b652529dd0f3acfc7bac6c46321e54ba6dcc299e55dbb6427c2c9f5ed65817059d3abcced76a1172b08890303cdff30c2c09595d455ecfdb392a487be2