Issue Summary

When P2 plugin expose OSGI component for migration path implementation, that is not found by migration assistant plugin.

This only applies for apps who:

• use `atlassian-app-cloud-migration-listener` library.
• and there is match between the groupId suffix and artifactId prefix. This is currently resulting in incorrect bundleKey formation

For example,
<groupId>com.vendor</groupId>
<artifactId>vendor-plugin-sample</artifactId>
results in bundlekey as `com.vendor.plugin-sample` whereas expected bundlekey is `com.vendor.vendor-plugin-sample`

Apps using `app-migration-osgi` and `app-migration-tracker` library are not impacted.

Steps to Reproduce

Expose an OSGI component from P2 plugin that uses `atlassian-app-cloud-migration-listener` library.

Expected Results

OSGI component exposed by P2 plugins should be visible to migration assistant plugin

Actual Results

OSGI component exposed by P2 plugin is not found by migration assistant plugin

Workaround

P2 plugins facing this issue are requested to override the following optional method of 
`DiscoverableListener` interface
 

String getServerAppKey() {

}