chore: tests in appropriate packages after split

[manusa]

Description

Follow up on #3844 / #3835.
Moved tests to the right modules and packages.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• Feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change
• Chore (non-breaking change which doesn't affect codebase;
  test, version modification, documentation, etc.)

Checklist

• Code contributed by me aligns with current project license: Apache 2.0
• I Added CHANGELOG entry regarding this change
• I have implemented unit tests to cover my changes
• I have added/updated the javadocs and other documentation accordingly
• No new bugs, code smells, etc. in SonarCloud report
• I tested my code in Kubernetes
• I tested my code in OpenShift

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
10 Code Smells

No Coverage information
0.0% Duplication

[shawkins]

Let's merge this one then I'll rebase #3858

[shawkins]

LGTM - the only thing that looks a little odd is the MapIndexer. Did it seem about the same amount of work to create that vs. targeted mocking?

[manusa]

the only thing that looks a little odd is the MapIndexer. Did it seem about the same amount of work to create that vs. targeted mocking?

It seemed like a more realistic and maintainable scenario, plus helped me understand a few things. I considered mocking, but it was turning out to be an extremely white-boxed test which didn't add much value.