Configure backend test coverage for sonar via jacoco

[MichaelGonzalezMurillo]

• [ ] Breaking change? (if so, please describe the impact and migration path for existing application instances)

What changes did you make? (Give an overview) Fixes #1537

Is there anything you'd like reviewers to focus on?

How Has This Been Tested? (put an "x" (case-sensitive!) next to an item)

• [ ] No need to
• [x] Manually (please, describe, if necessary)
• [ ] Unit checks
• [ ] Integration checks
• [ ] Covered by existing automation

Checklist (put an "x" (case-sensitive!) next to all the items, otherwise the build will fail)

• [x] I have performed a self-review of my own code
• [x] I have commented my code, particularly in hard-to-understand areas
• [x] I have made corresponding changes to the documentation (e.g. ENVIRONMENT VARIABLES)
• [x] My changes generate no new warnings (e.g. Sonar is happy)
• [x] I have added tests that prove my fix is effective or that my feature works
• [x] New and existing unit tests pass locally with my changes
• [x] Any dependent changes have been merged

Check out Contributing and Code of Conduct

A picture of a cute animal (not mandatory but encouraged)

[MichaelGonzalezMurillo]

[MichaelGonzalezMurillo]

[MichaelGonzalezMurillo]

[INFO] Check ALM binding of project 'com.provectus:kafka-ui_backend' [INFO] Detected project binding: NOT_BOUND

[INFO] Check ALM binding of project 'CronFire_kafka-ui' [INFO] Detected project binding: BOUND

Jacoco reports are being well generated but since the project is not bounded the results are not being send correctly.

Code wise we should be ok.