Add CI workflow

[KacperNapierski]

PR is direct response to #145 issue. I've created workflow that test linting and builds graphenex on windows and linux automatically on PR.

Description

The CI.yaml workflow activates when new changes in folders docker and graphenex are PR'ed/pushed into main branch. Workflow can also be started manually with workflow dispatch.
Workflow contains 3 jobs:

• Linter check - uses flake8 linter for checks. Is first job chronologically and is required for further tests to run. It's done this way to save time on building if basic test do not run successfully. I think it will be bonus after fixing existing lint problems.
• Linux setup - prepare ubuntu 22 machine with updated packages for graphenex installation, uses workaround from Ubuntu 22.04 installation tutorial  #121 and runs graphenex
• windows setup - install python 3.10.0, update packages, uses workaround from ImportError: cannot import name 'Mapping' from 'collections'  #127 and runs graphenex

Motivation and Context

Help with testing and stigmatization of development pipline

#145

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

[jxdv]

Hopefully we won't need those workarounds in the future, as we just need to replace some unmaintained libs. See: #135 newest comment.

[KacperNapierski]

That would be great and probably make gX more reliable for all users. If that happens it would be small change for workflow and I will just update it then.

[orhun]

This looks great, just had some comments/suggestions.

[KacperNapierski]

Let's not close #145 just yet. @KacperNapierski thanks for implementing this CI workflow, but I don't see the lint issues fixed here. Are you planning another PR for that?

I know @orhun said I can make 2 seperate PRs for linter and CI. My thought process was: if CI will work and check lintering everyone can make linter changes and test them as we progress with fixes

[jxdv]

Let's not close #145 just yet. @KacperNapierski thanks for implementing this CI workflow, but I don't see the lint issues fixed here. Are you planning another PR for that?

I know @orhun said I can make 2 seperate PRs for linter and CI. My thought process was: if CI will work and check lintering everyone can make linter changes and test them as we progress with fixes

Sure, makes sense.

[orhun]

Is this ready for re-review?

[KacperNapierski]

Is this ready for re-review?

I think so, linux and windows builds with poetry from code from this repository.