Hotfix add action ci (#227)

[diegorodriguez31]

Proposed changes

• Add start of GitHub Actions CI

• Change version to 4.1.2

• Remove mentions to Travis

• Change artifacts to upload in release

Types of changes

What types of changes does your code introduce to i-Code?

Put an x in the boxes that apply

• Bugfix (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 not work as expected)
• Documentation Update (if none of the other choices apply)

Issues closed by changes

• Close Continuous integration on Travis doesn't work anymore #226

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 agree with the CODE OF CONDUCT
• Lint and unit tests pass locally with my changes
• SonarCloud and Travis CI tests pass with my changes
• 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

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication