Architecture for LSP completion improvements

Feature Spec

Improvements to completions in the LSP typically fall into one of three categories:

• What contexts exist in which to generate completions and how can we detect that a position is in it?
  • e.g. Requesting completions within the right-hand side of an assignment is distinct from the left-hand side
• Given a context, what completions should be generated?
• Given a context and completion, how should it be displayed?

These categories are organized in the codebase via structs and traits to implement such that contributors can easily add new features.

Use Cases

Provides a large surface area of good-first-issues to improve the DX of Wing

Implementation Notes

This issue effectively requires https://github.com/winglang/wing/issues/1779, because without some testing in place contributors and maintainers may lack confidence in making LSP changes

Component

IDE Extension

• If you are interested to work on this issue, please leave a comment.
• Please vote by adding a 👍 reaction to the issue to help us prioritize.

Start by reviewing issue #1779, which this work depends on, then use the three completion categories in this specification to inspect the LSP implementation. Done means establishing an extensible structs-and-traits architecture for detecting contexts, generating completions, and displaying them, but this issue names no files or tests to run.