plugin v2 preview

[eternal-flame-AD]

very much WIP, expect big changes as I go.

Just sharing to get some early opinions.

TODO:

• Finalize the architecture
• A shim that takes a V1 plugin and returns a V2 plugin
• A test server and test client
• Scout existing issues to add missing features

[eternal-flame-AD]

@jmattheis Can you take a look when you have time before I do the server side integration? I think basic functionality and consistency tests should be all there.

[eternal-flame-AD]

I will leave the V1 plugin compatibility shim testing part suggestion to the next round in case there are disagreements about architecture, etc.

[jmattheis]

There are still some open discussions and I've unresolved one discussion which doesn't seem fixed yet, but this is only minor stuff, so from the architecture side this looks good.

[eternal-flame-AD]

I am starting to think about implementing auth plugins by allowing plugins to create and revoke user sessions, this can close some tickets about pluggable authentications. wdyt?

A broad idea would be just give the plugin a session signing key and expose a public API like /auth/exchange-code (or even just a temporary password) that exchanges a plugin endorsement with a real token.

[jmattheis]

I think oidc will cover most of the cases and there are already many services that proxy to oidc if you f.ex have a ldap server. I'm not sure if it's worth to implement the api for this, as we have to support this in android and this could be pretty difficult if it's generic.

Either way, this should be done separately from this migration.

[eternal-flame-AD]

Okay, I will open a concurrent PR on notify/website for plugin writing then and then the server side integration