fix: backward compatability for did-update

[aklkv]

as part of modernization I broke compatibility layer on did-update, this adds it back in self contained way

[NullVoxPopuli]

Don't we want the original macro conditions?

const untrack = (function () {
  if (macroCondition(dependencySatisfies('ember-source', '> 3.27.0-beta.1'))) {
    // ember-source@3.27 shipped "real modules" by default, so we can just use
    // importSync to get @glimmer/validator directly
    return importSync('@glimmer/validator').untrack;
  } else if (
    macroCondition(dependencySatisfies('ember-source', '>= 3.22.0-alpha.1'))
  ) {
    // we can access `window.Ember` here because it wasn't deprecated until at least 3.27
    // eslint-disable-next-line no-undef
    return Ember.__loader.require('@glimmer/validator').untrack;
  } else {
    // nothing needed here, we do not call `untrack` in this case
  }
})();

[aklkv]

yeah my thought was the same initially but I re-tested the original macro path and confirmed it still fails at runtime in the consumer (same DidUpdateModifier tracking assertion Assertion Failed: You attempted to update '...' on '...', but it had already been used previously in the same computation.), even though the build warning is gone; the runtime capability-based resolver is the only variant that fixed the real regression in practice.