Move build badge examples into services/ (#2234)

all-badge-examples is a common cause of merge conflicts. It’s difficult to adjust the badge categorization in that file – or to understand the diff – because it requires moving a block from one point to another. It’s much easier to edit a badge’s category in one place.

This starts the process of breaking up what’s left of that file, following up on the work from #1931. New-style services can only be in one category, which means legacy service examples have to be split along category lines. I split out separate legacy service classes where I could do so easily, leaving behind the ones which require more work, for one reason or another.

services/bugzilla/bugzilla.service.js

@@ -4,7 +4,34 @@ const LegacyService = require('../legacy-service')
 const { makeBadgeData: getBadgeData } = require('../../lib/badge-data')
 const { checkErrorResponse } = require('../../lib/error-helper')
 
+const documentation = `
+<p>
+  If your Bugzilla badge errors, it might be because you are trying to load a private bug.
+</p>
+`
+
 module.exports = class Bugzilla extends LegacyService {
+  static get category() {
+    return 'issue-tracking'
+  }
+
+  static get url() {
+    return {
+      base: 'bugzilla',
+    }
+  }
+
+  static get examples() {
+    return [
+      {
+        title: 'Bugzilla bug status',
+        previewUrl: '996038',
+        keywords: ['Bugzilla', 'bug'],
+        documentation,
+      },
+    ]
+  }
+
   static registerLegacyRouteHandler({ camp, cache }) {
     camp.route(
       /^\/bugzilla\/(\d+)\.(svg|png|gif|jpg|json)$/,