Max stack call error in prod mode with asserts (v5, v4)

[lifeart]

At the moment, if debug data is not stripped from prod build, we have recursion error.

Given: Prod build, assert function is not stripped.

1. Trying to access any key (id, for example) on just created model.

2. This code part is executed:

   data/packages/model/src/-private/attr.js

   Line 130 in 7243558

   return peekCache(this).getAttr(recordIdentifierFor(this), key);

3. And here we calling toString on record:
   

   data/packages/store/src/-private/caches/instance-cache.ts

   Line 68 in 7243558

   assert(`${String(record)} is not a record instantiated by @ember-data/store`, RecordCache.has(record));

4. And we going here:

   data/packages/model/src/-private/model.js

   Line 501 in 7243558

   return `<model::${this.constructor.modelName}:${this.id}>`;

Where we access this.id and here is GOTO: 1.

[lifeart]

It's not an real issue, but may appear on non ember-cli/embroider envs.

In codebase we have quite alot of cases, referring to model id.
One of possible workarounds - try to prevent nested toString calls on model.

{
  #isToStringInProgress = false;
  toString() {
    if (this.#isToStringInProgress) {
      return `<${this.constructor.modelName}:unknown>`;
    }
    this.#isToStringInProgress = true;
    try {
      return  `<model::${this.constructor.modelName}:${this.id}>`; 
    } finally {
      this.#isToStringInProgress = false;
    }
  }
}

[runspired]

this is why non ember-cli/embroider envs still need a build config (and build plugin). Not running our final build step will produce a very un-tested and dramatically different library with significantly degraded performance characteristics

[runspired]

Closing as nothing for us to do here on this ticket, tracking for broader compat is in #8147 and for embroider/vite is in #8103