Add ddev start for the host command

[stasadev]

The Issue

• fix: dont auto start host custom commands, fixes #2688 ddev#5603

How This PR Solves The Issue

In the next release of DDEV, there will be no automatic project start when the host command is executed, so this PR adds the necessary ddev start here.

[rfay]

I think this approach will break people who get the addon with earlier ddev versions. Probably better to see if it's set before taking action, don't do anything if var not set. In "launch" and family we know it should be set but here we don't.

[stasadev]

Yeah, right, didn't test it with a stable DDEV.

Fixed by setting the default value only when the variable is unset.
${DDEV_PROJECT_STATUS-running} https://stackoverflow.com/a/16753536

[rfay]

Thanks, this seems like a good technique, looks to me like syntax is wrong? At least I've only ever used ${VAR:-default}

[rfay]

I like the technique, it's a good one. But it should be like this, right?

Suggested change

	if [ "${DDEV_PROJECT_STATUS-running}" != "running" ]; then
	if [ "${DDEV_PROJECT_STATUS:-running}" != "running" ]; then

[stasadev]

No, this can give an unexpected result for the case when $DDEV_PROJECT_STATUS is defined but empty.

bad:

DDEV_PROJECT_STATUS="" && echo "status=${DDEV_PROJECT_STATUS:-running}"
status=running

good:

DDEV_PROJECT_STATUS="" && echo "status=${DDEV_PROJECT_STATUS-running}"
status=

[stasadev]

POSIX: Parameter Expansion Examples: https://stackoverflow.com/a/16753536/8097891

[stasadev]

I tested this behavior on macOS and it works the same way.
I'm going to merge ${DDEV_PROJECT_STATUS-running}" because it works exactly as it should.