Nested JSON Objects are Case Sensitive Hashtables

**Explanation:**
When parsing a nested object within the HTTP body of the request, the nested object is de-serialized as a case-sensitive hashtable in PowerShell. They top-level object is converted to a case-insensitive table, however nested object's aren't.

{
"nestedObject": {
"PropertyName": "TEST"
},
"id": 0,
"PropertyName": "TEST"
}

No source file or test is named. Start by reproducing the HTTP-body deserialization with the nested JSON example in a PowerShell function, then trace the worker's request parsing entry point and compare top-level and nested property lookup. Done means nested object properties behave case-insensitively like the top-level object, with coverage for the provided example.

Written by the indexing model from the issue text.