(features): support for plugin components developed locally

[philcali]

Feature Description

We need to add transparent support for a plugin component like we do generic components.

Use Case

It's currently not trivial to test plugin components.

Proposed Solution

When we identify that the local component is a plugin, we can instead copy the jar over the the DUT's trusted plugins directory. I see this as a "ComponentPreparationService" impl to handle this behavior, or modification to an existing one.

Other
Add detailed explanation, stacktraces, related issues, links for us to have context, etc

• 👋 I may be able to implement this feature request
• ⚠️ This feature might incur a breaking change