[Client bug]: Nullable Reference Types are misleading

Describe the bug
Properties are marked as nullable which should never be null.

To Reproduce
Consider the following method and assume I have <Nullable>enable</Nullable> set in my .csproj file:

private async Task<List<MailFolder>> GetMailFolders(UserItemRequestBuilder user)
{
    var folders = await user.MailFolders.GetAsync();
    return folders.Value;
}

When building, I get two nullability warnings, CS8602 (folders might be null) and CS8603 (folders.Value might be null). The first one I could understand. Something went wrong with the request so the response is null. The second, however, I have a hard time wrapping my head around. Collection data structures should rarely be null. In the case something went wrong, they are often simply empty. I looked into the SDK code and saw that pretty much every property is marked as nullable, even properties which can never be null, like an Id. This doesn't help the developer at all. I just upgraded from v4 to v5 and my build is now littered with incorrect nullability warnings.

Expected behavior
Only properties which actually can be null, are marked as nullable.

Client version
5.2.0

Desktop (please complete the following information):

• OS: macOS
• Version: Ventura (13.2.1)

Start by reproducing the nullable warnings in the GetMailFolders example with Microsoft Graph SDK v5.2.0, then inspect the generated SDK properties involved in the response and model types. Done means properties that cannot be null no longer produce incorrect nullable warnings while genuinely nullable properties remain annotated.