ci: patch inquirer baseUI to fix Node 24 ERR_USE_AFTER_CLOSE in Gen 1 e2e

[sarayev]

Description of changes

Gen 1 e2e tests that drive amplify add function — function_migration,
http_migration, and custom_query_mutation_extension — fail on Node 24.

Root cause. These tests use the vendored nexpect harness, which answers the
"Do you want to edit the local lambda function now?" confirm prompt and then
immediately sends EOF (sendConfirmNo().sendEof()). EOF closes the underlying
readline interface. The legacy inquirer bundled with the installed
@aws-amplify/cli-internal then runs its teardown in lib/ui/baseUI.js#close(),
which calls this.rl.pause() on the now-closed readline. On Node ≤ 22 that was a
silent no-op; on Node 24 it throws ERR_USE_AFTER_CLOSE: readline was closed,
which surfaces to the user as 🛑 There was an error adding the function resource
and fails the test.

Fix. A committed, idempotent post-install patch of the installed CLI's
inquirer baseUI.js. The patch guards the pause() call:

this.rl.pause();   ->   if (!this.rl.closed) { this.rl.pause(); }

Why a post-install patch (category-api-only, no CLI republish)

The crash lives in inquirer as consumed by @aws-amplify/cli-internal, which
is installed from the local registry during e2e setup and is out of this repo's
control. Patching it post-install keeps the fix entirely within
amplify-category-api and avoids republishing @aws-amplify/cli-internal. The
proper upstream fix (migrating the Gen 1 confirmPrompt usage to
confirmContinue) is a separate, lower-urgency follow-up in amplify-cli.

Changes

New post-install patch helper

codebuild_specs/scripts/patch-inquirer-baseui.js — idempotent: given one or
more baseUI.js paths it rewrites the unguarded this.rl.pause(); to the
guarded form, and no-ops if already patched, not found, or no match. Heavily
commented to explain the Node 24 ERR_USE_AFTER_CLOSE reason.

Wire patch into CLI install

shared-scripts.sh _installCLIFromLocalRegistry() — after the
npm install -g @aws-amplify/cli-internal line, a find rooted at
$(npm root -g) matches hoisted or nested inquirer installs and invokes the
helper on each baseUI.js.

Issue #, if available

N/A

Description of how you validated changes

Validated locally on Node 24.14.0 against an installed cli-internal@14.5.1:

• Before (unpatched): reproduced the crash both via the e2e-core
  addFunction helper (sendConfirmNo().sendEof()) and a direct
  printf 'N\n\x04' | amplify add function. Output:
  Error [ERR_USE_AFTER_CLOSE]: readline was closed at Interface.pause ... at PromptUI.close (inquirer/lib/ui/baseUI.js:60:13), 🛑 There was an error adding the function resource, exit code 1.
• After (patched): the same direct repro exits 0 and the e2e-core helper
  returns SUCCESS.
• Verified the helper script is idempotent (second run reports "already
  patched"), patches both hoisted and nested layouts, and safely no-ops on
  missing files. bash -n shared-scripts.sh passes.

Checklist

• PR description included
• yarn test passes
• Tests are changed or added
• Relevant documentation is changed or added (and PR referenced)
• New AWS SDK calls or CloudFormation actions have been added to relevant test and service IAM policies
• Any CDK or CloudFormation parameter changes are called out explicitly

[sarayev]

Closing as superseded. This PR was a test-infra stopgap that post-install-patched the e2e harness's inquirer baseUI to keep Gen1 e2e green on Node 24. The real product fix now lives in amplify-cli: aws-amplify/amplify-cli#14949 (fix(cli-internal): guard confirmPrompt against node 24 readline crash), which guards confirmPrompt against the Node-24 ERR_USE_AFTER_CLOSE for all callers (incl. amplify add function → openEditor). Once that ships in a published cli-internal release, the Gen1 e2e picks it up via the verdaccio→npm uplink and no harness patch is needed. The A/B run already proved the approach (batch 0023882e: function_migration/http_migration/custom_query_mutation_extension all PASS on Node 24 with the guard). Closing in favor of #14949.