VBLang Repo lacks clarity

The vblang repo lacks clarity, particularly in terms of what can be expected to be worked on. @bandleader described [it as "a mess" in ](https://github.com/dotnet/vblang/issues/248#issuecomment-362023338).

From @bandleader's comments:

> - there are tons of issues with no response from Microsoft at all
> - many issues are describing scenarios that should be combined into one feature (must create issue for the full feature, describe which issues this supersedes. take in the most accepted syntax/ideas of the other issues, then CLOSE them)
> - some issues are not clearly defined, written in hard-to-understand English, or propose changes that cause grammar ambiguity (not everyone > understands compilers) or solve too narrow a scope of scenarios, and the issue needs to be clarified, corrected, and sometimes integrated > into a new issue.

Also:
- there are several issues that are different proposed solutions for the same problem.

I absolutely want to provide clarity to this repo and avoid anyone being forced to reopen existing issues.

Drawing ideas from other repos helps consistency, but this repo is unique in many ways. I think we will be best served if this repo serves as one mechanism for strengthening community. I assume this repo has been frustrating at times, and my goal is to reduce that.

This discussion is only for the VBLang repo. Other repos, like the Roslyn repo is an intense working repo that requires different and generally stricter management.