Nullable annotations support

[mkArtakMSFT]

Summary

What's covered as part of this effort:

• Enable nullable-annotations for the aspnetcore repo (tracked separately)
• Enable nullability enforcement in project templates
• Make generated code, scaffolding and any other pieces of code that we emit in to a user's project nullable-aware or better, nullable enabled.

People with more context

@pranavkm, @JamesNK

Motivation and goals

1-2 paragraphs, or a bullet-pointed list. What existing pain points does this solve? What evidence shows it's valuable to solve this?

In scope

A list of major scenarios, perhaps in priority order.

Out of scope

Scenarios you explicitly want to exclude.

Risks / unknowns

How might developers misinterpret/misuse this? How might implementing it restrict us from other enhancements in the future? Also list any perf/security/correctness concerns.

Examples

Give brief examples of possible developer experiences (e.g., code they would write).

Don't be deeply concerned with how it would be implemented yet. Your examples could even be from other technology stacks.

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We will evaluate the request when we are planning the work for the next milestone. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[mkArtakMSFT]

Closing as we now have multiple issues tracking this.