migrate some services from examples to openApi part 44; affects [sonar]

[chris48s]

Refs #9285

Made a start on this service family. Submitting a WIP PR for now, just to lick the cookie. I'll finish it later in the week.

[github-actions]

	Messages
📖	✨ Thanks for your contribution to Shields, @chris48s!

Generated by 🚫 dangerJS against 36c76e9

[chris48s]

I've tried to provide working examples for as many of these as possible, but there are a couple of these where I couldn't find any working example - in those cases, the tests are already mocks so I can't grab one from there and I wasn't able to find any examples in public repos on github. I've just left those with plausible but non-working values.

[PyvesB]

Should there be an alert_status example?

[PyvesB]

Should there be a sqale_debt_ratio example?

[chris48s]

In both the cases you've flagged the metric param doesn't really do anything - we show the same value either way. I think this is a case where we changed the route at some point in the past and the enum is there to keep the old name working but we only document the new one.

[PyvesB]

Okay, I guess we could implement a route redirector at some point instead!

[chris48s]

There are one or two other services where we do something like this. Here's another example that springs to mind:

shields/services/vaadin-directory/vaadin-directory-version.service.js

Lines 8 to 15 in 1ed5440

	static route = {
	base: 'vaadin-directory',
	pattern: ':alias(v|version)/:packageName',
	}
	static openApi = {
	'/vaadin-directory/v/{packageName}': {
	get: {

I don't really have strong views about replacing with a redirect, but maybe that pattern of calling the param :alias makes it clearer?