Ci graphql server

[Valecant]

Proposed changes

Describe the big picture of your changes here to communicate to the
maintainers why we should accept this pull request.
If it fixes a bug or resolves a feature request, be sure to link to
that issue.

Types of changes

What types of changes does your code introduce to the project: Put
an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Documentation (improve documentation)
• Continuous Integration (functionality that improve automation or testing)
• Breaking change (fix or feature that would cause existing
  functionality to not work as expected)

Checklist

Put an x in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to
ask. We're here to help! This is simply a reminder of what we are going
to look for before merging your code.

• I have read the CONTRIBUTING doc
• I have signed the Contributor License Agreement
• I have updated the RELEASE NOTES
• I have added tests that prove my fix is effective or that my
  feature works
• I have added necessary documentation (if appropriate)
• Any dependent changes have been merged and published in
  downstream modules

Further comments

If this is a relatively large or complex change, kick off the discussion
by explaining why you chose the solution you did and what alternatives
you considered, etc...

[github-actions]

CLA Assistant Lite bot All contributors have signed the CLA ✍️

[Valecant]

To test Graphql is mandatory to set up the Configuration API
first, once completed:

$ cd configuration-api
$ npm install
$ npm test

The results of the tests will be visible on the console

[chicco785]

include test as part of githubactions