Add more granular support and server 2025 support for versioning

[bwatters-r7]

After checking out the latest build info stuff, it looks like Server 2025 is a bit of a combo breaker in loose parity on build numbers to workstation build numbers.
Rather than keep the original broad Windows 10 vs Windows 11 categories, I went ahead and split the Workstation/Servers and did the builds independently. I also added the subversion where appropriate. This results in code I can only apologize for, but it does provide a clear path forward and more granular results.
I'm hoping this does not break anything, as modules should be using the versioning we added recently.
Since Windows Server naming convention is..... imaginative, it might confuse someone when they're given Windows Server 2004. I almost changed this to be Windows 2016_2004, but that could also be confusing, as I think Server 1909 technically is a variant of 2016, that's not how it was marketed.
Anyway- I wanted to add Server 2025 support and figured Id throw this out as a conversation piece, too.

msf6 payload(cmd/windows/http/x64/meterpreter_reverse_tcp) > sessions -i -1
[*] Starting interaction with 1...

meterpreter > sysinfo
Computer        : WIN2025__B7EC
OS              : Windows Server 2025 (10.0 Build 26100).
Architecture    : x64
System Language : en_US
Domain          : WORKGROUP
Logged On Users : 2
Meterpreter     : x64/windows

[*] Starting interaction with 2...

meterpreter > sysinfo
Computer        : WIN10_1511_8379
OS              : Windows 10_1511 (10.0 Build 10586).
Architecture    : x64
System Language : en_US
Domain          : WORKGROUP
Logged On Users : 2
Meterpreter     : x64/windows