Document query string variables for key without value becoming value without key

It is quite common to use URL query string keys without values for boolean flags, e.g. `?foo` rather than `?foo=true`. This page does not document how those are handled.

It seems that the returned `NameValueCollection` contains these key-only query variables as no-key/null-key values.

That also means multiple flags are returned as a comma separated list of values/query-var-keys as a string - which is suboptimal for handling such query variables, when more than one can occur.

---
#### Document Details

⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*

* ID: cb6855ee-43a7-3a40-bef2-8b455dd4443c
* Version Independent ID: 5b1274ec-c193-769c-986e-2c95852477d0
* Content: [HttpRequest.QueryString Property (System.Web)](https://docs.microsoft.com/en-us/dotnet/api/system.web.httprequest.querystring?view=netframework-4.7.2#System_Web_HttpRequest_QueryString)
* Content Source: [xml/System.Web/HttpRequest.xml](https://github.com/dotnet/dotnet-api-docs/blob/master/xml/System.Web/HttpRequest.xml)
* Product: **dotnet-api**
* GitHub Login: @dotnet-bot
* Microsoft Alias: **dotnetcontent**

Leggi xml/System.Web/HttpRequest.xml e confrontalo con la documentazione collegata di HttpRequest.QueryString. Verifica come vengono rappresentate nella NameValueCollection restituita le variabili di query composte solo da una chiave e più flags, quindi documenta questo comportamento e le sue implicazioni per i consumer. Il lavoro è completato quando la pagina spiega accuratamente entrambi i casi.

Scritto dal modello di indicizzazione a partire dal testo della issue.