Introduce *IfNecessary Load Actions

[jrista]

feat: add load if necessary action variants

 + Add LoadIfNecessary action
 + Add LoadAllIfNecessary action
 + Add LoadManyIfNecessary action
 + Add LoadPageIfNecessary action
 + Add LoadRangeIfNecessary action
 * Export new actions from public api
 + Add new operators for if necessary loads
 + Add new effects for if necessary loads
 * Include new effects in standard modules
 * Export new effects from public api
 + Add stateNameOfEntity utility function
 * Update builders to use new entityStateName function

Issue #144

---

feat: add defaultMaxAge to entity operator

 * Introduce to `defaultMaxAge` to IEntityOptions
 + Add EntityAge with predefined common ages for use with `defaultMaxAge`
 * Update @Entity decorator to support passing name in only or options or both
 > Move key decorator tokens into entity-tokens.ts
 > Extract entity decorator into its own file entity-decorator.ts
 > Extract key decorator into its own file key-decorator.ts
 * Update index/public api to reference all exports from new locations
 * Added EntityAge enum to public api
 * Removed all imports from '../..'

Issues #144 #141

---

feat: reorg action files and introduce *IfNecessary load actions

 * Refactor all actions into more files for easier management
   * Loads into load-*-actions.ts
   * CUURDS into create|update|upsert|replace|delete-actions.ts
   * DeleteByKeys into delete-by-key-actions.ts
   * Edits into edit-actions.ts
   * Selections into selection-actions.ts
   * Deselections into deselection-actions.ts
 + Add new *IfNecessary loader actions for each type of load
 + Add tsdoc to all load actions
 * Update library index/public api to reference all actions from new files
 * Update all otehr action references throughout library
 ^ Bump library version to 0.5.0-beta.3

Phase #1: This is an initial refactoring of action files for the if-necessary work

Issue #144

[jrista]

NOTE: DO NOT MERGE!!

This PR is just phase one of the work for this feature. Additional work is being done to integrate the new *IfNecessary actions into the effects. Do not merge until the second phase of the work has been committed.

[jrista]

It looks like our performance tests are failing. I'm a little concerned, as when I originally created those, the actual run times were well below (fractions of) the actual times I "expected". For example, the 50ms time for the 10k load was about 5x longer than the actual results I was getting at the time, which was ~10ms on average, and the 2000ms for the 1m load was about 2-3x longer. We are now topping those times consistently... I think I'd like to figure out why before we merge this. I would hate to hurt our performance numbers that much.

[jrista]

I'm starting to think the performance difference might in part be due to some changes in the jest libraries. I upgraded jest a minor version, and I even recall at the time that I had some issues after just with the normal run times of the full set of unit tests.

When I run the performance tests within WebStorm, they all succeed consistently, however the run times for 10k and 100k are now about half the expected times, rather than ~1/5th the expected times, and the run time of the 1m test is close to the 2s expected time.

It may be prudent to try and set up a lighter weight set of performance tests at some point...this might be testable just with node.js, as the reducer is just a function in the end.

[schuchard]

Seem's others are seeing issues at v24 and v25 jestjs/jest#7732

[jrista]

Interesting...I thought I'd only upgraded a minor version, but I think I upgraded jest previously as well, and that may have been one or even two major versions in that case. Well...its not a huge issue, although it may result in tests randomly failing. When I run locally in webstorm, I seem to be around half or so the specified thresholds for those performance tests. Not as good as they were originally, but better than I'm expecting.