Repo housekeeping - Labels cleanup 🧹

• -review-:
  • Double-check with @DonJayamanne if he wants to review any of these issues
  • Have a conversation with @luabud and @brettcannon on what to do with these issues (close, prioritize) and then delete the label 🚮
• Add a spike label (same color as the needs ... labels, can be needs spike) and update spikes accordingly (remove the needs spec label) [@luabud]
  • Update bot to consider this new label [@brettcannon]
• Deal with cause-* labels [@karthiknadig]
  • Rename cause-VSCode to partner ask
  • Delete other cause-* labels
• Make the description of type-code health more descriptive (covers everything internal: CI, testing, refactoring of the codebase, etc…)
• upstream-*:
  • upstream-ptvsd: @karthiknadig will handle them
  • upstream-language server: review, prioritize, close or transfer then delete the label
  • upstream-vscode: delete the label 🏃‍♀️
• Review needs upstream fix label (prioritize, close, transfer) and delete the label
• feature-:
  • feature-intellisense:
    • Expand its description to include autocompletion, code documentation and code navigation
    • Reassignfeature-code documentation and feature-code navigation issues to feature-intellisense and then delete these labels
  • Rename all feature- labels to area-
  • Add area-internal label (for non-user facing work)
    • Assign feature-* and feature-editor experience issues accordingly
    • Delete feature-*🚮
  • Rename feature-editor experience to area-editor-* (user-facing grab-all)

[kimadeline]

If the team is up for it we could use the housekeeping time slot to comb through old issues and close the ones that aren’t relevant anymore (if any). The secondary suggestion of starting with area-intellisense was because I stumbled upon #10079.

[kimadeline]

Not label-related, but still housekeeping:

Ongoing

• Delete stale/merged branches
• Close GitHub issues that are marked as complete
• Clean up P1s for what is not a real P1 anymore

One-time actions

• Do a formatting pass on the issue references in the codebase to leverage GitHub issues integration in VS Code: https://github.com/microsoft/vscode-python/pull/12279