Draft: Abstract build queueing logic

What does this MR do?

This does:

• Move all Database matching out of RegisterJobService into Ci::Queueing::LegacyDatabaseService
• Does not change any logic, rather just moves all matching into a new place
• Defines a skeleton to introduce new queueing mechanisms based on Runner type, ex. allowing to implement @grzesiek idea from #322972
• Allows to try and implement many concurrent ideas along side that can be enabled/disabled one-by-one

Related to: #322972

Does this MR meet the acceptance criteria?

Conformity

• 📋 Does this MR need a changelog?
  • I have included a changelog entry.
  • I have not included a changelog entry because _____.
• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• Tested in all supported browsers
• Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• Label as security and @ mention @gitlab-com/gl-security/appsec
• The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• Security reports checked/validated by a reviewer from the AppSec team