Fix backtick evaluation in add-script and run-script inline scripts

[Copilot]

The devcontainer CLI generates devcontainer-features.env with option values in double quotes (SCRIPT="echo \date`"). When the wrapper sources this file via . ./devcontainer-features.env, bash command-substitutes backticks before install.sh` ever runs — so the script content is already corrupted.

Fix

Re-read SCRIPT verbatim from devcontainer-features.env using awk at the top of install() in both features, bypassing shell evaluation entirely:

if [ -f ./devcontainer-features.env ]; then
    SCRIPT=$(awk '/^SCRIPT="/{sub(/^SCRIPT="/,"");v=$0;f=1;next}f{v=v"\n"$0}END{if(f){sub(/"$/,"",v);printf"%s",v}}' ./devcontainer-features.env)
fi

Without this fix: SCRIPT="echo \hostname`"→SCRIPT=echo myhost With this fix:SCRIPTretains the literal `` echohostname` ``

Tests

• add-script: new test-backtick scenario writes a script containing `hostname` and asserts the file contains the literal backtick syntax
• run-script: new test-backtick scenario runs echo backtick_test=`hostname` and asserts the substitution actually executed (non-empty value written to output file)

Versions

Both features bumped 1.0.0 → 1.1.0.

[sebst]

One test fails

[Copilot]

One test fails

Fixed in c2ea83f. The run-script scenario test was failing with tmpScript: unbound variable — the EXIT trap (trap 'rm -f "${tmpScript}"' EXIT) fired after install() returned, but tmpScript was declared with local so it was out of scope when the trap ran. Removing local makes it a global variable that the EXIT trap can access.