Makefile uses quickstart binary in quickstart target

[halms]

Preflight checklist

• I could not find a solution in the existing issues, docs, nor discussions.
• I agree to follow this project's Code of Conduct.
• I have read and am following this repository's Contribution Guidelines.
• This issue affects my Ory Cloud project.
• I have joined the Ory Community Slack.
• I am signed up to the Ory Security Patch Newsletter.

Describe the bug

The Makefile uses a quickstart binary in the quickstart and quickstart-dev targets.
This change was introduced in #2206.

It looks to me, as if the change was initially planned to include a quickstart binary in the EXECUTABLES line, as is shown in the review to #2206.

I don't know if this is just a plain mistake or if some software package actually includes a quickstart binary that works as a replacement for docker-compose. I could not find anything googling for a quickstart binary (but as this is a very generic term, it is actually hard to find something specific).

My suggestion would be, to change this back to using Compose.
Ideally this would be the new Compose v2, which is called via docker compose and not docker-compose anymore.

Also, the docker build command in the quickstart-dev target is different from the line in the docker target.
I would suggest to just have the quickstart-dev target depend on the docker target.

I am happy to create a PR changing the Makefile but would like to clarify this here before.

Reproducing the bug

• Run make quickstart in kratos directory
• Command fails with
  /bin/bash: line 1: quickstart: command not found

Relevant log output

No response

Relevant configuration

No response

Version

Current master, but bug present since v0.9.0

On which operating system are you observing this issue?

No response

In which environment are you deploying?

No response

Additional Context

No response