RTI: Changes for performance

[ndduc01]

Notes

Hold off on merging this

• Added support for multi thread kafka consumption
• Added Hikari config to support multi thread
• Removed chain and complicated try catch for better bug tracing
• Removed step 2 and step 3 kafka event, all three steps is combined as a single event now.
• Convert some JPC to JDPC (very few)
• Removed Transactional to support multi threading
• Removed ID Cache in SRTE
• Updated ID logic in SRTE to ensure it pull a distinct id for every new thread
• Added DP_ Prefix to RTI Topic for better managing

JIRA

• Related story: Jira Ticket

Checklist

• PR focuses on a single story.
• New unit tests added and ensured they pass.
• Service has been tested in local and it works as expected.
• Documentation has been updated for this code change (if needed).
• Code follows the Java Coding Conventions (https://www.oracle.com/java/technologies/javase/codeconventions-programmingpractices.html).

Types of changes

What types of changes does this PR introduces?

• Bugfix
• New feature
• Breaking change

Testing

• Does this PR has >90% code coverage?
• Is the screenshot attached for code coverage?
• Does the gradle build pass in your local?
• Is the gradle build logs attached?

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

[sonarqubecloud]

Quality Gate failed

Failed conditions
30.8% Coverage on New Code (required ≥ 90%)

See analysis details on SonarQube Cloud