Closes ngrx#2363

Closes ngrx#2363

Closes ngrx#2417

Closes ngrx#2431

These checks are enabled by default in NgRx 9

…grx#2231)

Closes ngrx#2232

…ata guide (ngrx#2428)

)

…ponent package (ngrx#2046)

…#2383)

Closes ngrx#2334

Closes ngrx#2454

* fix(component): add docs overview

closes ngrx#2442

* Update projects/ngrx.io/content/guide/component/index.md

Co-Authored-By: Tim Deschryver <[email protected]>

Co-authored-by: Tim Deschryver <[email protected]>

…ing` (ngrx#2463)

…rx#2453)

- Switches toObservableValue to just use rxjs `from`. This will ensure it works with all
  types that `rxjs` is compatable with. Also, the checks in `toObservableValue` were redundant if
  `from` was used.  For example, if `x` is `Observable` from rxjs, then `from(x) === x` would be `true`.
  `from` does all of the necessary checks. Also, `from` will do the work of figuring out of it happens
  to be an observable that has interop with RxJS, or is an observable from another instance
  of rxjs (in node_modules, Node scenario).
- Also `x == null` will only return `true` if `x` is `undefined` or `null`.
- Fixes the return types of `toObservableValue` to be more true to form. If you return
  `Observable<X> | Observable<Y> | Observable<Z>`, it's really no different than `Observable<X | Y | Z>`,
  because there's no static/synchronous way to narrow the type of the `Observable` to say, `Observable<X>`
  in either scenario.
- Removes unecessary types in favor of more obvious explicit types
- Removes superfluous isObservable-type assert function
- Removes unused assertion methods. Not sure what those were used for, as they were exported, but two
  were ill-advised, as they were doing type-narrowing by iterating over an array, making it an O(n) operation
  just to narrow a type.

…grx#2475)

The `@angular/cli` as of version 9 requires minimum yarn v.1.13.0 to work

…rx#2477)

ngrx#2461)

Closes ngrx#2404

Closes ngrx#2363

Closes ngrx#2363

…ko/platform into mockstore-logsless

Closes ngrx#2363