Update the MAX_TOKEN_SIZE in Sspi.java to 48000

[JStroom]

We ran into an issue with Windows authentication, that was caused by the Sspi.MAX_TOKEN_SIZE being too small for our current Windows version. We are using JNA 5.9.0.

According to the article below the default MAX_TOKEN_SIZE has been updated from 12.000 to 48.000 in recent windows version (Windows 11).
I want to propose to update the MAX_TOKEN_SIZE in jna to 48.000.

https://docs.microsoft.com/en-us/troubleshoot/windows-server/windows-security/kerberos-authentication-problems-if-user-belongs-to-groups#calculating-the-maximum-token-size

[dblock]

See #261 for a similar discussion. The conclusion was a "yes, go for it, but ...".

[dbwiddis]

See #261 for a similar discussion. The conclusion was a "yes, go for it".

Looks like the final conclusion was to remove it from the API in a major version bump, that got missed? :)

[dblock]

I think I am with @matthiasblaesing in that issue that says we should keep it, but the caller needs to know that the API the are calling can fail with insufficient buffer and handle that like in https://github.com/Waffle/waffle/blob/208077d732dc9081571971f4aca2bdf408b463cb/Source/JNA/waffle-jna/src/main/java/waffle/windows/auth/impl/WindowsSecurityContextImpl.java#L127 for example.

Removing works for me too, but then we need to be more careful. I wonder though why we would inflict a backwards incompatible change on everyone while the caller still needs to handle insufficient buffer size.