Release of i-Code CNES 4.1

[begarco]

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

This pull resquest contains enhancement and bug fixes for i-Code 4.0.

New features

• FEATURE i-Code should not crash on checker error #198 > i-Code should not crash on checker error
• FEATURE Simplify logged information #201 > Simplify logged information

Fixed bugs

• BUG Correction erreur COM.xxx #131 > Correction erreur COM.xxx
• BUG Test files may have a "contains" instead of an "equals" to check the location value #147 > Test files may have a "contains" instead of an "equals" to check the location value
• BUG IndexOutOfBoundsException while analyzing an empty Shell script #197 > IndexOutOfBoundsException while analyzing an empty Shell script
• BUG JAXB is still used but missing in icode-library #200 > JAXB is still used but missing in icode-library

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

List here all issues closed by your changes. Use a list of items like - [x] Close #0

• Close Correction erreur COM.xxx #131
• Close Test files may have a "contains" instead of an "equals" to check the location value #147
• Close IndexOutOfBoundsException while analyzing an empty Shell script #197
• Close i-Code should not crash on checker error #198
• Close JAXB is still used but missing in icode-library #200
• Close Simplify logged information #201

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]

SonarCloud Quality Gate failed.

6 Bugs
3 Vulnerabilities (and 0 Security Hotspots to review)
159 Code Smells

0.0% Coverage
0.0% Duplication