Require plugins to declare their annotations

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})`
    ]
}

Start by tracing the bsc plugin lifecycle and the proposed onPluginConfigure hook. Define how plugins declare annotation names, arguments, types, and multiple signatures, then determine how those declarations feed editor help and unknown-annotation diagnostics. Done means the breaking behavior and v1.0 compatibility plan are settled and the requirements are covered.