Test match using regular expressions

[ilmanzo]

Description of the changes Changed integration tests to match output with a regular expression, to keep in consideration that compiled executable can be run from a temp location ( /tmp/$RANDOM_DIR )

Related issue(s) Fixes #39

Type of change Please select one or multiple of the following options:

• [x] 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 not work as expected)
• [ ] Code cleanup (refactoring or improving code quality)
• [ ] Documentation update (adding or updating documentation, updating README)

Checklist:

• [x] I have read the CONTRIBUTING document.
• [x] 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.
• [x] All new and existing tests passed.

Additional information Add any other information or screenshots about the pull request here.

[jkfran]

Thank you so much for reporting and working on a solution.

Can you please fix the conflicts? 🙏🏼

[ilmanzo]

Thank you so much for reporting and working on a solution.

Can you please fix the conflicts? 🙏🏼

done, please note that running the test in parallel may conflict, because they spawn a service on the same port. Either use different port for each test, or run the tests with cargo test -- --test-threads=1 to make them sequential.

[ilmanzo]

this also fixes cargo clippy complaints, so we can close #41 as well