[enhance] Improve normalizr type expressiveness

[ntucker]

Motivation

Solution

• Fake nominal typing for schema types (since they have pretty similar signatures).
  • future: should change to tracking return value of normalize as that can encode proper typings. We can use the schema provided and build on that to pretty convincingly manifest the algo. This can replace the giant ResultType and Denormalized block.
• Add missing readonly member schema
• Include Array in Schema and SchemaList def
• Add greedy resolution to Entity in ResultType and Denormalized generics.
  • This means if we only have SchemaDetail or SchemaList it will resolve to T and T[] respectively. While we don't actually know this - it enables a broad base class definition for our REST shapes. In the future a better solution is to simply make those shapes a mixin and encourage more often writing own shapes from scratch.

Open questions

Should we just try to fix the normalize/denormalize algo now?

[ntucker]

faking nominal typing.