"devkit avs devnet start" fails for default user flow

Summary

The standard devkit avs devnet start command fails for a blank/standard newly created AVS.

Expected Behavior

devkit avs devnet start command starts the avs

Actual Result

2025/07/08 09:21:55 Executing script: deployContracts
2025/07/08 09:21:55 Stopping containers
2025/07/08 09:21:55 ✅ Stopped container devkit-devnet-hello-devkit
2025/07/08 09:21:55 ✅ Removed container devkit-devnet-hello-devkit
2025/07/08 09:21:55 Stopped devnet container running on port 8545, project.name hello-devkit
2025/07/08 09:21:55 deploy-contracts failed: deployContracts failed: failed to run script .devkit/scripts/deployContracts: fork/exec .devkit/scripts/deployContracts: no such file or directory

Steps to reproduce

devkit avs create hello-devkit-test
cd hello-devkit
cp .env.example .env
cat > .env <<EOF
# Ethereum holesky fork URL used for AVS devnet
L1_FORK_URL=https://young-wild-wind.ethereum-holesky.quiknode.pro/438cf7546f522bc8444c36bbe701b65896e51c8e
# Ethereum holesky fork URL used for AVS devnet
L2_FORK_URL=https://young-wild-wind.ethereum-holesky.quiknode.pro/438cf7546f522bc8444c36bbe701b65896e51c8e
EOF
devkit avs build
devkit avs devnet start

Start with the devkit avs devnet start entry point and trace how it invokes .devkit/scripts/deployContracts; the reported failure is that this script cannot be found after devkit avs build. Reproduce with the commands in the issue and confirm that a newly created AVS can start its devnet successfully without the missing-file error.