suggestion: centralize CLI plugin registration in cortex

[evaline-ju]

Feature Description

Leveraging a new cortex plugin through the CLI would require CLI code changes to register it. Plugins are defined in cortex so it should be the single source of truth.

Proposed Solution

Centralize registration in cortex so that the CLI shouldn't need to change per plugin

Want to contribute?

• I would like to work on this issue.

[esnible]

My first thought is to update the CLI everytime AuthBridge gets a new plugin merged.

For real plugins we need a mechanism that isn't static linking. The most popular approach is https://github.com/hashicorp/go-plugin . I haven't used this mechanism, but it seems to be the most popular.

[evaline-ju]

Fair, I mainly wanted to reduce per-plugin toil, not necessarily imply static linking as a long-term solution. Will update the issue body