Azurite is more lenient than TableStorage when parsing a query

Recently had an error in a non-dev environment because of the differences in how Azurite and actual table storage interprets a query.

I accidentally wrote `Or` instead of `or` in my query and azurite was fine with that, things worked, but when it was run on table storage it gave me a syntax error because the `or` has to be lowercase.

Azurite is probably more lenient because of some of the toLowerCase code found in [QueryParser.ts](https://github.com/Azure/Azurite/blob/main/src/table/persistence/QueryInterpreter/QueryParser.ts)
```typescript
private visitOr(): IQueryNode {
const left = this.visitAnd();

if (this.tokens.next(t => t.kind === "logic-operator" && t.value?.toLowerCase() === "or")) {
const right = this.visitOr();

return new OrNode(left, right);
} else {
return left;
}
}
```

Not sure where in the priority the consistency beween azurite and tablestorage in production are, since they are inherently very different technologies.
Just wanted to let you know, if it was helpful, since it had me wondering for quite a while.