run aqa-tests sanity perf test complaint "configure_liberty.sh: line 56: cd: ${env.PERF_ROOT}: No such file or directory"

**Describe the bug**
run aqa-tests sanity perf test complaint "configure_liberty.sh: line 56: cd: ${env.PERF_ROOT}: No such file or directory"

**To Reproduce**
```bash
export JDK_VERSION=17
export JAVA_HOME=${HOME}/software/jdk/2022-05/dragonwell-17.0.3.0.3+7-GA
export TEST_JDK_HOME=$JAVA_HOME
export PATH=$JAVA_HOME/bin:$PATH
export USE_TESTENV_PROPERTIES=true
export JDK_IMPL=hotspot
export BUILD_LIST=perf
cd aqa-tests
./get.sh
./compile.sh
```

**Expected behavior**
get the correct ${env.PERF_ROOT}

**Screenshots**

**Additional context**
Add any other context about the problem here.

Start by reproducing the reported sequence with JDK_VERSION=17, BUILD_LIST=perf, and USE_TESTENV_PROPERTIES=true from the aqa-tests directory. Inspect configure_liberty.sh around line 56 and trace how PERF_ROOT is set or consumed by get.sh and compile.sh. Done means the sanity perf setup no longer attempts to cd into the literal ${env.PERF_ROOT} path.

Written by the indexing model from the issue text.