Separate branch protection builders from "full" builders

Scope

This task covers the refactoring (and config reorganization) of separating branch protected builders logic from "complete" builders (where necessary).

Branch protection builders can not run the full set of tests as required for ensuring released packages are correct, so they must be separated, but must not impact the full test coverage for packages we do release. Unfortunately at this point, this is the case and has to be fixed.

Details - user facing

Currently we have a set of builders that are part of branch protection, but are also correlated to platforms that we release packages from.

Given that branch protection builders test less that complete builders (to expedite builds), we need to separate the logic in two sets.

We will have:

• Branch protection builders
  For example: amd64-debian-12-protected running main (and a few other) suites.
  We will call this set of tests: "The branch protection suite"
  Currently it is:

  main

  spider

  spider/bg

  spider/bugfix

  spider/feature

  spider/regression/e1121

  spider/regression/e112122

• Complete builders
  For example: amd64-debian-12 running all suites as part of a "normal" test run.

Implementation details

As a follow-up change, given further refactoring we can remove this suffix and use a "Label" to filter such builders, but that will be decided as part of a secondary task.

NOTE

There is a difference between the build config for builders such as amd64-debian-12 and amd64-debian-12-autobake. This holds true for RPM based builds too.

The builders that create release packages, (those ending in autobake) never have a full suite of tests run, as it happens in old buildbot. This will be addressed in MDBF-988, it is not part of this task.