[Xzzz]

Summary

Re-lands the native Bugzilla::API::V1::Bugzilla controller (/rest/version, /extensions, /timezone, /time, /jobqueue_status), reverted in ef9e9b0 because a monitoring service calls /rest/jobqueue_status with ?api_key=<key>.

That call works on native routes since 2073282 (deprecated ?api_key= / ?Bugzilla_api_key= fallback in the native login), so the original change comes back unchanged. Last core resource of 2057358: only extension endpoints remain on the legacy REST server.

Changes

• Revert of the revert ef9e9b0, i.e. the original 65642f5:
  • Add Bugzilla/API/V1/Bugzilla.pm (GET + OPTIONS on the 5 paths, same responses as before)
  • Remove Bugzilla/WebService/Bugzilla.pm, Resources/Bugzilla.pm and the Bugzilla dispatch entry
• WS_DISPATCH now only holds the extensions registered through the webservice hook; Bugzilla/WebService.pm POD updated accordingly.
• qa/t/rest_legacy_credentials.t checks Bugzilla_login/Bugzilla_password on GET /rest/component-watching, still served by the legacy server, instead of /rest/version.
• qa/t/rest_bugzilla.t: GET /rest/jobqueue_status?api_key=<key> returns 200.
• general.md: the resources still on the legacy auth path are now only some extension endpoints.

Test plan

• GET /rest/version, /rest/timezone anonymously: 200, same JSON as before
• GET /rest/extensions, /rest/time, /rest/jobqueue_status anonymously: 401 login_required; with X-Bugzilla-API-Key: 200
• GET /rest/jobqueue_status?api_key=<key>: 200
• GET /rest/component-watching with Bugzilla_login/Bugzilla_password: 200, and an error with bad credentials

References

• Bugzilla link: 2061445
• Part of 2057358
• Unblocked by 2073282