fix: Issue 534 transformation tests failing on some platforms

[boxanm]

Description

Summary:

The 3D Transformation utests were failing on Ubuntu Bionic with Eigen 3.3.4, in contrast to all other platforms tested with Eigen 3.4. I added a non-zero epsilon precision value to Eigen's isApprox call for Rotation and Rotation+Scaling tests. My guess is the two versions of Eigen treat zero epsilon precision values differently; hence the tests weren't failing with 3.4.0. Fixes https://github.com/norlab-ulaval/libpointmatcher/issues/534

Changes and type of changes (quick overview):

• Added a non-zero epsilon precision value to Eigen's isApprox in failing Transformation utest.

• ---

Checklist:

Code related

• [x] I have made corresponding changes to the documentation (i.e.: function, class, script header, README.md)
• [x] I have commented hard-to-understand code
• [x] I have added tests that prove my fix is effective or that my feature works
• [x] All tests pass locally with my changes (Check README.md #Contributing for local testing procedure using libpointmatcher-build-system)

PR creation related

• [x] My pull request base ref branch is set to the develop branch (the build-system won't be triggered otherwise)
• [x] My pull request branch is up-to-date with the develop branch (the build-system will reject it otherwise)

PR description related

• [x] I have included a quick summary of the changes
• [x] I have indicated the related issue's id with # <issue-id> if changes are of type fix
• [x] I have included a high-level list of changes and their corresponding type
  • Types: feat fix docs style refactor perf test build ci chore revert
  • Breaking changes: <type>!
  • Reference: see commit_msg_reference.md in the repository root for details

---

Note for repository admins

Release PR related

• Only repository admins have the privilege to push/merge on the default branch (ie: master) and the release branch.
• Keep PR in draft mode until all the release reviewers are ready to push the release.
• Once a PR from release -> master branch is created (not in draft mode),
  • it triggers the build-system test
  • (in-progress) and it triggers the semantic release automation

[sonarcloud[bot]]

Quality Gate failed

Failed conditions

20.6% Duplication on New Code (required ≤ 3%)

See analysis details on SonarCloud

[boxanm]

The arm64 build randomly falls on the build farm. Since this issue wasn't encountered locally on an arm machine, we assume it was due to the CPU architecture virtualization. I'm therefore bypassing the branch protections.