[proposal] Plugin-agnostic Execution

[eddie-knight]

Problem

As the developer of a Privateer plugin, I would like to give my users an "easy button" to run the plugin from Privateer as it is intended, without requiring my plugin users to understand the Privateer ecosystem.

Potential Solution

1. Docker Container — this could be a container that takes runtime arguments to execute known or ad-hoc plugins. Supporting known plugins is essential for caching, so that users are not taxing public resources by downloading common items every time there is a run. Ad-hoc will also be helpful, so that the container is not exclusive of new or uncommon plugins.
2. GitHub Action — After the container exists, building a correlated GitHub action should be relatively straightforward.