Generates InjectedTest in a named package.

[Vlatombe]

This makes the test friendlier to JUnit results collection when working with PCT or in multi-module projects in general.

The package name is derived from groupId and artifactId, but can also be provided through configuration if needed.

Testing done

Existing IT parent-4x exercises this, though doesn't make any assertion about the actual package name being used. Could add a new one if needed.

Submitter checklist

Preview Give feedback

1. Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
2. Ensure that the pull request title represents the desired changelog entry
3. Please describe what you did
4. Link to relevant issues in GitHub or Jira
5. Link to relevant pull requests, esp. upstream and downstream changes
6. Ensure you have provided tests - that demonstrates feature works or fixes the issue

[basil]

+1, seems reasonable to use a unique name for each plugin to facilitate test result visualizations.

[jglick]

Looks helpful. Should not break any tools which run -Dtest=InjectedTest since that will match a test inside a package.