Bug 1646017 - Promise.any errors should not assume async stack data is available. r=jorendorff,anba

This test assumed that AggregateError stack traces would include frames from
across the asynchronous boundary, which is not guaranteed to be the case. This
test originally passed because Promise.any was only enabled on Nightly and
the Nightly release had the "javascript.options.asyncstack" pref enabled by
default, which guaranteed that async frames were guaranteed to be captured.

Now that bug 1601179 has landed, this is no longer the case because the realm
is required to be a debuggee before async frames will be included in the trace.

Differential Revision: https://phabricator.services.mozilla.com/D79936

js/src/tests/non262/Promise/any-stack.js

@@ -1,4 +1,4 @@
-// |reftest| skip-if(!Promise.any)
+// |reftest| skip-if(!xulRuntime.shell) -- needs async stack capture
 
 function toMessage(stack) {
   // Provide the stack string in the error message for debugging.

js/src/tests/non262/Promise/any.js

@@ -1,5 +1,3 @@
-// |reftest| skip-if(!Promise.any)
-
 // Smoke test for `Promise.any`, test262 should cover the function in
 // more detail.