Require plugins to declare their annotations

[TwitchBronBron]

Require plugins to declare their annotations ahead of time so we can provide better editor help and also validation.

This is a breaking change to bsc because annotations would be validated for their existence, so perhaps it's a good candidate for v1.0?

Requirements:

• plugins must declare all of their annotations, which include name and any arguments and their types. For future compatibility, we should support an array of signatures (even if we only support one signature at the moment).

Benefits:

• we can provide intellisense for annotations
• we can show diagnostics when using unknown annotations

Possible implementation:
There's a new plugin lifecycle hook where plugins can declare various settings. Perhaps something like this:

onPluginConfigure(event){
    //should this be brighterscript style code? Or json? 
    this.annotations = [
         `inline()`,
        `suite(suiteConfig as { name: string, timeout: number})`
    ]
}

[markwpearce]

Can this be v1.1 ?

[TwitchBronBron]

Maybe? The risk is that if we launch without it, it would be a breaking change to land it later in v1, becuase we would essentially enforce that all annotations are pre-registered.