Replacement of prompt service with custom code

[tuler]

While working on the startup feedback, I ended up redoing a lot of the work that was done at PRs #177 and #153
So this PR includes some of those changes, but also the new startup feedback.
Please check my individual commits on this PR, and compare them to the ones at #177

The startup feedback works by creating a listr2 of tasks where each task is a polling of docker compose ps <service> for the healthy status of a service. For each service there is a service name, but also a healthySemaphore which is the name of the service that indicates healthy status.

For example, the graphql is a service, but we need to wait for the proxy service to be healthy to report access to graphql, as it is proxied through it.

I only implemented healthy status checks, which means that every service that is part of the startup feedback will now require a health check configuration. We are still missing health check config for the following services:

• health check for espresso
• health check for explorer
• health check for bundler
• health check for paymaster

[changeset-bot]

🦋 Changeset detected

Latest commit: e778033

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@cartesi/cli	Major

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

Coverage Report for ./apps/cli

Status	Category	Percentage	Covered / Total
🔵	Lines	27.77%	293 / 1055
🔵	Statements	27.85%	298 / 1070
🔵	Functions	27.56%	51 / 185
🔵	Branches	26.19%	121 / 462

File Coverage

File	Stmts	Branches	Functions	Lines	Uncovered Lines
Changed Files
apps/cli/src/base.ts	0%	0%	0%	0%	24-140
apps/cli/src/commands/rollups/start.ts	0%	0%	0%	0%	11-286
apps/cli/src/commands/rollups/status.ts	0%	0%	0%	0%	8-49

Generated in workflow #363 for commit e778033 by the Vitest Coverage Report Action

[tuler]

Total startup time in my machine with --services graphql is taking from 5 to 6 seconds.

[endersonmaia]

Missing healthchecks for services you described and defined the dependency.

[endersonmaia]

I suggest normalizing healthcheck parameters between services (interval, start_time, etc.)

[tuler]

I suggest normalizing healthcheck parameters between services (interval, start_time, etc.)

Done.
Is timeout 1a good enough for pg_isready?

[endersonmaia]

--verbose is not working, but I'll consider this PR approved, and we can tackle this --verbose behavior on another PR