Disable allow_reuse_address (SO_REUSEADDR) on Windows

[jiasli]

Fix #10578: az login hangs when more than one instances of az login are launched at the same time on Windows or WSL

The root cause is that HTTPServer can't detect port is in-use on Windows.

To repro, launch az login but do not continue in the browser. Then run az login from another terminal and continue with the login. One of the az instance will get stuck.

This PR disables HTTPServer.allow_reuse_address so that the correct routine is resumed.

---

This checklist is used to make sure that common guidelines for a pull request are followed.

• The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

• I adhere to the Command Guidelines.

[yugangw-msft]

Try to test CI, will close and re-open

[qwordy]

Just for testing.

[qwordy]

I can't cancel my approval now, which can be done before the permission change. Please don't merge before a real approval.

[qwordy]

I think we don't need to support multiple az login at same time since we don't support multiple accounts. We can let all other az login fail if there is an az login running. az login should not interleave.
And if we support multiple az login, add write locks to token files. I've seen broken accessTokens.json because of concurrent write. The content is interleaving.

[qwordy]

Test how to revoke approval.

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[fengzhou-msft]

I'm wondering why the original _is_wsl() is ignoring the passed in perameter platform_name, release and calls _get_platform_info() to overwrite them?

[jiasli]

Seems to be some forgotten logic.

[jiasli]

Did more research on the behavior of SO_REUSEADDR and SO_EXCLUSIVEADDRUSE on Windows and saw these discussions:

• Drop usage of SO_EXCLUSIVEADDRUSE on Windows python-trio/trio#928
• Windows: SO_REUSEADDR allows listening on occupied port tornadoweb/tornado#550
• https://stackoverflow.com/a/14388707/2199657
• https://bugs.python.org/msg152697
• https://docs.microsoft.com/en-us/windows/win32/winsock/using-so-reuseaddr-and-so-exclusiveaddruse
• More: https://github.com/search?q=SO_REUSEADDR+windows+in%3Atitle+is%3Aissue&type=Issues

The common solution is to not set SO_REUSEADDR or SO_EXCLUSIVEADDRUSE:

• Drop usage of SO_EXCLUSIVEADDRUSE on win32 (#928) python-trio/trio#1108
• Don't set SO_REUSEADDR on Windows tornadoweb/tornado#551
• disable SO_REUSEADDR on windows rpclib/rpclib#278
• More: https://github.com/search?q=SO_REUSEADDR+windows+in%3Atitle+is%3Apr&type=Issues

Therefore, setting allow_reuse_address = False should be the right path here, which makes SO_REUSEADDR not being set on Windows:

https://github.com/python/cpython/blob/3.9/Lib/socketserver.py#L464-L465

        if self.allow_reuse_address:
            self.socket.setsockopt(socket.SOL_SOCKET, socket.SO_REUSEADDR, 1)

[welersonlisboa]

#26180

[jiasli]

@welersonlisboa, this PR is not relevant to #26180.