Expose GraphQL endpoint in CLI

[endersonmaia]

This pull request includes several changes to the @cartesi/cli package to expose a GraphQL endpoint and provide options to enable or disable it. The changes include updates to the CLI commands, Docker Compose configurations, and related services.

Major changes:

• Expose GraphQL endpoint:

  • Added a major change entry in the .changeset/heavy-penguins-act.md file to document the exposure of the GraphQL endpoint.

• CLI command updates:

  • Added a new option --disable-graphql to the registerRunCommand function in apps/cli/src/commands/run.ts to allow users to disable the local GraphQL service.
  • Updated the registerRunCommand function to include the docker-compose-graphql.yaml file if the GraphQL service is not disabled.

• Docker Compose configuration:

  • Added a new docker-compose-graphql.yaml file in apps/cli/src/node to define the services required for the GraphQL endpoint, including database creation, migration, and the GraphQL service itself.

Minor changes:

• Validator Docker Compose adjustments:
  • Removed the GraphQL-related configuration from the docker-compose-validator.yaml file to avoid conflicts and ensure proper setup. [1] [2]

[changeset-bot]

🦋 Changeset detected

Latest commit: b5e77f5

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	30.9%	293 / 948
🔵	Statements	31%	298 / 961
🔵	Functions	34.22%	51 / 149
🔵	Branches	27.25%	121 / 444

File Coverage

File	Stmts	Branches	Functions	Lines	Uncovered Lines
Changed Files
apps/cli/src/commands/run.ts	0%	0%	0%	0%	7-247

Generated in workflow #287 for commit b5e77f5 by the Vitest Coverage Report Action

[tuler]

Rebased

[fabiooshiro]

LGTM!

[tuler]

This case be closed when we finalize PR #116, because it's handled there through --services graphql.
It can still be open, for reference, until we merge that other one.

[tuler]

I think this can be closed now.