Configure source maps for legible stack traces in Lambda logs

[lpsinger]

          I think that https://github.com/nasa-gcn/gcn.nasa.gov/pull/2754 helped, but I recently got two copies of https://gcn.nasa.gov/circulars/38476. Here's the server log:

2024-12-09T05:56:29.521Z	6cb876d0-b08b-4341-9fcd-8a9a69c783f8	ERROR	Invoke Error 	{
    "errorType": "Error",
    "errorMessage": "ThrottlingException: Rate exceeded",
    "stack": [
        "Error: ThrottlingException: Rate exceeded",
        "    at Object.intoError (file:///var/runtime/index.mjs:46:16)",
        "    at Object.textErrorLogger [as logError] (file:///var/runtime/index.mjs:684:56)",
        "    at postError (file:///var/runtime/index.mjs:801:27)",
        "    at done (file:///var/runtime/index.mjs:833:11)",
        "    at fail (file:///var/runtime/index.mjs:845:11)",
        "    at file:///var/runtime/index.mjs:872:20",
        "    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)"
    ]
}

It's hard to tell what is timing out because the stack trace is referring to minified source.

Originally posted by @lpsinger in #2659 (comment)