Performance issues with ModelUtils._coerce and coerceArray

Describe the bug

The way ModelUtils._coerce uses coerceArray is inefficient, and is causing it to show up as 20% of my application's CPU usage in profiler runs under a create heavy workload.

The problem code is this in juggler:

    try {
      // Coerce val into an array if it resembles an array-like object
      val = coerceArray(val);
    } catch (e) {
      // NOOP when not coercable into an array.
    }

Throwing and catching an error is much more expensive than returning a value, and nearly every call to _coerce hits this try/throw/catch path.

A variant of coerceArray that doesn't throw, but instead returns [arrayVal | undefined, coerced: boolean] I think would fix the performance problem here.

Logs

No response

Additional information

No response

Reproduction

design issue

lib/model-utils.js の 498〜503 行付近から始めます。ここで ModelUtils._coerce は try/catch パス内から coerceArray を呼び出しています。coerceArray の動作と、issue で説明されている create-heavy なワークロードを確認し、そのうえで coercion が例外の繰り返しによるコストなしに既存の動作を維持することを検証し、profiling で改善を確認します。