0.3.2 `localstack` command not found

Nobody has claimed this yet.

From GHA logs:

```
Run if [ "$USE_PRO" = true ]; then
if [ "$USE_PRO" = true ]; then
if [ "x$LOCALSTACK_API_KEY" != "x" ]; then
echo "WARNING: LOCALSTACK_API_KEY is deprecated, please use LOCALSTACK_AUTH_TOKEN instead."
fi
if [ "x$LOCALSTACK_AUTH_TOKEN" = "x" -a "x$LOCALSTACK_API_KEY" = "x" ]; then
echo "WARNING: LocalStack Auth Token not detected, please verify your configuration..."
fi
CONFIGURATION="DNS_ADDRESS=127.0.0.1 ${CONFIGURATION}"
IMAGE_NAME="${IMAGE_NAME:-localstack/localstack-pro:${IMAGE_TAG}}"
else
IMAGE_NAME="${IMAGE_NAME:-localstack/localstack:${IMAGE_TAG}}"
fi

CONFIGURATION="IMAGE_NAME=${IMAGE_NAME} ${CONFIGURATION}"
docker pull ${IMAGE_NAME} &
export CI_PROJECT=
eval "${CONFIGURATION} localstack start -d"

if [ "$SKIP_WAIT" = false ]; then
localstack wait -t ${LS_WAIT_TIMEOUT:-30} # Let users configure the timeout via env variable
fi
shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
env:
GITHUB_REPO_NAME: TrueRowing/hydrow-identity
NPM_CONFIG_USERCONFIG: /home/runner/_work/_temp/.npmrc
NODE_AUTH_TOKEN: XXXXX-XXXXX-XXXXX-XXXXX
GH_ACTION_ROOT: ./../../_actions/LocalStack/setup-localstack/v0.3.2
LOCALSTACK_AUTH_TOKEN: ***
SERVICES: cognito-idp,kms
IMAGE_TAG: latest
INSTALL_AWSLOCAL: true
USE_PRO: true
CONFIGURATION:
SKIP_WAIT: false
/home/runner/_work/_temp/c586c0b3-9067-483a-b653-4b8a7d5a08b0.sh: line 17: localstack: command not found
```

The relevant action step:
```
- name: configure localstack
uses: LocalStack/setup-localstack@v0.3.2
with:
image-tag: 'latest'
install-awslocal: 'true'
env:
LOCALSTACK_AUTH_TOKEN: ${{ secrets.LOCALSTACK_AUTH_TOKEN }} # If using Pro
SERVICES: cognito-idp,kms # Example services to start
```

Fails everytime with a process exited with error code 127.

Start with the GitHub Actions workflow step using LocalStack/setup-localstack@v0.3.2 and compare it with the logged shell commands and environment. Reproduce the workflow, trace why the localstack executable is unavailable, and verify that the command is present and the setup completes without exit code 127.

Written by the indexing model from the issue text.