perf: Optimize mutator methods definition check

[sylvainpolletvillard]

The way ObjectModel currently validates mutative method calls on list models implies to validate the whole model for every mutation. This is suboptimal and a perf killer for some usecases (see https://github.com/sylvainpolletvillard/ObjectModel/issues/94)

Proposed solution:

• specify for every mutator method which arguments to validate and cast
• check assertions on the testing clone, but no longer check the whole definition

I did not find a case where a list element had to be checked again, that was not part of the mutator method arguments.

Current list of arguments indexes to check def / autocast is:

Array

• fill : [0]
• push; [0..n],
• splice: [2..n],
• unshift: [0..n]

Map

• set: [0] (key), [1] (value)

Set

• add: [0]

[sylvainpolletvillard]

Done and released as v3.7.1

cc @gotjoshua: you should no longer have a perf penalty by assigning the items one by one