fix: Do not call of caching service during routing to check sticky session if not needed

[pavel-jares-bcm]

Description

There is the class DeterministicLoadBalancer. This class is reposible for deterministic routing of request. It uses header X-InstanceId or last used used server to implement sticky session.

The issue is in the order of taken actions to process the request. If the request contains a token (the user could be detected) it always call caching service, even the value is not used there.

The impact:

more I/O and performance degradation for authenticated request
it could failed when Caching service is down (even the call is not needed)

Linked to #4510
Part of the # (epic)

Type of change

Please delete options that are not relevant.

• fix: Bug fix (non-breaking change which fixes an issue)
• feat: New feature (non-breaking change which adds functionality)
• docs: Change in a documentation
• refactor: Refactor the code
• chore: Chore, repository cleanup, updates the dependencies.
• BREAKING CHANGE or !: Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• My code follows the style guidelines of this project
• PR title conforms to commit message guideline ## Commit Message Structure Guideline
• I have commented my code, particularly in hard-to-understand areas. In JS I did provide JSDoc
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• The java tests in the area I was working on leverage @nested annotations
• Any dependent changes have been merged and published in downstream modules

For more details about how should the code look like read the Contributing guideline

[taban03]

Please provide a description in the PR

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
89.8% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud