Show that a Lambda reuses a "dirty" environment in subsequent requests.

lambda-process-isolation-issue.js

// The first time this lambda is invoked, you will see a console message, "Hello, world!"
// If you invoke the lambda again soon thereafter, you will see "Your message has been hijacked"
// due to console.log being overridden from the first invocation.

exports.handler = async (event) => {
  console.log("Hello, world!");

  global.console.log = (msg) => {
    console.error("Your message has been hijacked");
  };
};