[Bug]: Projects with long descriptions (>~16k) don't emit FileVersion in the produced DLLs

### Issue Description

When compiling a versioned csproj with a Description property that is bigger than 16k, the FileVersion (+ other attributes) of the DLL stop being emitted.

I've attached a repro where the `ConsoleApp4` project has a description of length 17k while `ConsoleApp5` has 16k. When compiling the two DLLs and comparing their file attributes:

I am not sure why this is happening but if the Description property has a limit shouldn't it be enforced with an error during the build rather than silently passing with missing info in the built DLL?

My use case here is I want to bundle the CHANGELOG.md file when I publish packages, so it's reasonable to add a `Substring`, to the `Description` but should I have to do that?

### Steps to Reproduce

Steps to reproduce:
1. Run `dotnet build` on the root of the solution
2. Look at the generated DLLs and the respective bin/Debug folders

[BugRepro.zip](https://github.com/dotnet/msbuild/files/11372201/BugRepro.zip)

### Expected Behavior

The File version / Product version should be populated in ConsoleApp4.dll

### Actual Behavior

The File version / Product version is empty in ConsoleApp4.dll

### Analysis

_No response_

### Versions & Configurations

msbuild -version
MSBuild version 17.5.1+f6fdcf537 for .NET Framework
17.5.1.16304

dotnet --version
7.0.203

Start with BugRepro.zip and run dotnet build on the root solution, comparing the generated DLL attributes for ConsoleApp4 and ConsoleApp5. Trace how the Description property becomes assembly metadata; done means the version and product version are populated for the project with the 17k description, or the build reports an explicit limit error.

Written by the indexing model from the issue text.