envsubst -no-unset blows up on ${FOO:=}

It seems that an empty default value is treated as if a default value has not been provided.

Expected:

```console
~ $ go install github.com/a8m/envsubst/cmd/envsubst@v1.4.2
~ $ go/bin/envsubst -no-unset <<< 'value: ${FOO:=}'
value:
~ $ echo $?
0
~ $
```

Got:

```console
~ $ go install github.com/a8m/envsubst/cmd/envsubst@v1.4.2
~ $ go/bin/envsubst -no-unset <<< 'value: ${FOO:=}'
variable ${FOO} not set

~ $ echo $?
1
~ $
```

Look at the parsing logic for variable substitution in the source code, likely in a file like parse.go or subst.go. The bug is that ${FOO:=} with an empty default is incorrectly flagged as unset when -no-unset is used. Run the existing tests to see how defaults are handled, then add a test case for this scenario and fix the parsing to treat empty defaults as valid.

Written by the indexing model from the issue text.