perf(store): tree-shake errors and warnings

[arturovt]

• the StoreValidators class has been tree-shaken in production
• Ivy warnings have been tree-shaken in production
• most other errors and warnings have been tree-shaken in production

[markwhitfeld]

@arturovt, trying to reach you on Slack, could you log in?

[splincode]

Very cool 😎

[arturovt]

The CI seems to be happy 😄

[splincode]

Awesome )

[markwhitfeld]

@arturovt Do you think that we could do a refactoring PR with a cleanup like this:

// in some global .d.ts
const ngxsDevRuntime = typeof ngDevMode === 'undefined' || ngDevMode;

// then somewhere 
ngxsDevRuntime && funcToBeShaken();

This is much cleaner IMO. Hoping that it works.
Error throwing is a bit tricky (throw is its own kind of statement), but could be done this way:

// in some internal dev util
function throwForDev(error: Error) { throw error; }

// for errors we could do this
ngxsDevRuntime && throwForDev(new Error('Some Error'));

I chose the name ngxsDevRuntime to avoid confusion with the developmentMode module option.

[arturovt]

@markwhitfeld I'll check that!