Lint the Wing SDK source code for invalid wing annotations

Summary

Compiler warning when JSII manifest has invalid wing annotations

Feature Spec

In the SDK, each resource has a preflight class and an inflight interface that get associated together to form the resource API in the Wing compiler. This association is made with a docstring annotation (as its a piece of metadata we can easily inspect using the .jsii manifest). See for example:

https://github.com/winglang/wing/blob/221c5c4843354a597c676933cbef1e2cc1667621/libs/wingsdk/src/cloud/bucket.ts#L37-L42

But since this is annotation, it's possible for it to contain an invalid value. If we could that the annotation is valid (and fail to import the library if it doesn't), then we could avoid bugs like this one: https://github.com/winglang/wing/pull/701

Use Cases

Preventing bugs in Wing libraries that are written in TypeScript

Implementation Notes

Maybe this logic could be added in wingii, or in the jsii_importer part of the compiler.

Not every class or construct in a Wing library needs to have an @inflight annotation (for example, a resource might exist without any inflight methods). But if the annotation exists, it should be valid.

Component

Compiler

Start with the annotated resource example in libs/wingsdk/src/cloud/bucket.ts, then inspect the wingii or jsii_importer areas mentioned in the issue. Determine where the .jsii manifest is imported and make an existing @inflight annotation reject invalid values while allowing resources without the annotation; done means invalid SDK annotations fail library import.