Microsoft.Extensions.ObjectPool has unique assembly version convention relative to all the other Microsoft.Extensions and maintenance packages

### Is there an existing issue for this?

- [x] I have searched the existing issues

### Describe the bug

All this discussion will be regarding the .NET Framework targeted assemblies, in the various nuget packages.

Microsoft.Extensions.ObjectPool 9.0.9 on nuget.org has assembly version 9.0.9.0

But *every single other* .NET maintenance package and Microsoft.Extensions.* package has the servicing number in the **4th** integer position: 9.0.0.9.

### Expected Behavior

In a .NET Framework app where we have to manually manage binding redirects, this peculiarity is a pain to deal with. While I recognize that you probably cannot ship the 10th servicing release of this assembly with a _lower_ version of 9.0.0.10, can you please at least for .NET 10 fix this assembly to use the same assembly versioning convention as all the other .NET packages?

**I want to see**

Microsoft.Extensions.ObjectPool 10.0.0.0
Microsoft.Extensions.ObjectPool 10.0.0.1
Microsoft.Extensions.ObjectPool 10.0.0.2

**I do NOT want to see**

Microsoft.Extensions.ObjectPool 10.0.0.0
Microsoft.Extensions.ObjectPool 10.0.1.0
Microsoft.Extensions.ObjectPool 10.0.2.0

### Steps To Reproduce

_No response_

### Exceptions (if any)

_No response_

### .NET Version

9.0.9

### Anything else?

_No response_