We landed stricter detection of deprecation warnings in #51431. This was primarily achieved by using the --throw-deprecation flag. This, however, will be caught if the offending code is surrounded by a try-catch, which means any deprecated API used synchronously inside of a promise or in an async-await context will be caught and not exit the process, which in turn most likely means that it will go unnoticed.

We should improve this by crashing the process even in these cases (by utilizing process.on('warning')).