Implement Chrome 133+ support

[BRUHItsABunny]

Since Chrome 133 the TLS fingerprint is changing due to this feature:
https://chromestatus.com/feature/5149147365900288

I found that others are also running into this problem here: #330

It looks like a "full" implementation might be bigger than just extending the current application settings extension, as per another implementation here:
bogdanfinn/utls@fe91add

Opening this PR as a draft to discuss how we should move forward on this, I've also implemented this for the time being as it might be enough to address this (at least for my use case)

[Juktong]

Since the previous codepoints are coded in file exttype_values.go, it would be a good idea to also update it as well.

[BRUHItsABunny]

I noticed some TLS errors especially on Google domains while using my branch. I have updated it to support the new application settings code point in the ECH as well to fix those errors.

[mingyech]

Looks good, added some suggestions

[RonaldinhoL]

rename ApplicationSettingsExtension to applicationSettingsExtension break my exist custom spec

[RonaldinhoL]

Just duplicating the ApplicationSettingsExtension would be cleaner. These changes force unnecessary updates to too many spec settings.

[BRUHItsABunny]

I understand, some of my own modules also broke with those changes and wasn't sure if that was the expectation with the approach that was requested.
I made some changes that achieve both goals at the same time (1 only 1 place to implement the extension being written to the wire, 2 no breakages with the pre-existing patterns that expect the SupportedProtocols slice to be available and exported)