Provide maintainer information for prefix/wildcard hack plugins

[daniel-beck]

Reproduction steps

Several permissions files in this repository declare artifact names that do not match the actual component artifact IDs to work around the limitation of requiring one file per artifact ID, which can be cumbersome for multimodule repositories.

The most notable one of those is probably https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-aws-java-sdk.yml which governs more than a dozen separate plugins.

As a side effect the update site does not find corresponding entries in https://reports.jenkins.io/maintainers.index.json for these plugins, and subsequently the plugins appear to have no maintainers on plugins.jenkins.io.

This practice should stop to allow jenkins-infra/update-center2#654 to move forward.

Expected Results

https://reports.jenkins.io/maintainers.index.json contains maintainer information for plugins whose permissions are currently specified using the "wildcard hack".

Actual Results

It does not.

Anything else?

It looks like the following plugins are currently using this hack:

• aws-java-sdk-*
• mina-sshd-api-*

The bom-* does as well, but since it's not a plugin, its maintainers are not exposed elsewhere.

[timja]

Also #3538 (comment)