area-analyzer issues house-keeping

[srawlins]

We have some house-keeping to do for issues tagged with area-analyzer. Here are some small, concrete issues:

• [ ] analyzer-recovery issues should all be verified as not-yet-fixed, then moved to area-front-end front-end-fasta-recovery
• [x] analyzer-crash-report issues should be deduplicated.
• [x] analyzer-nnbd-migration issues should be reviewed, with totally-unplanned items closed.
• [ ] analyzer-completion issues should be reviewed in light of the amazing NLP work. I suspect many could be closed.

There are, of course, many other house-keeping chores that could be done, but I want this issue itself to be a well-defined with a defined close state.

[srawlins]

CC @bwilkerson Regarding the analyzer-completion idea, it is not my intention at all to assign work or even priority. Just an idea I had, regarding our heap of area-analyzer issues. Let me know if that task should be scrapped or something.

[bwilkerson]

We should definitely go through the completion related issues. That's probably work that @jwren and I should take on.