[BUG] typology processor cache key undefined

[Justus-at-Tazama]

Bug Report

Description

When the Tazama full-service option is deployed (option 2) from the full-stack-docker-tazama and a transaction is submitted to the TMS API, the transaction is seen to arrive at the typology processor from all the rules, but the transaction does not complete and no result is delivered.

This does not happen when the rule-901 option is deployed (option 3).

Steps to Reproduce

1. Deploy the full-service (option 2) (Full-Stack-Docker-Tazama repo tazama/multi-tenant-testing branch - run start.bat)
2. Send in a pacs.008 and pacs.002 transaction from Postman (Postman repo tazama/multitenancy branch - 2. Full-service-test.postman_collection.json)
3. No results are delivered to the tadproc

Prior to step 2, you can monitor the cache contents by:
Connecting to the valkey container:
docker container exec -it <container-id> valkey-cli
enter monitor to show the cache I/O
Then send in the transactions from Postman
With the exception of the EFRuP, the tenantId in the cache key is undefined for all rule processor results in the typology processor:

Also, I'm not sure if this is part of the issue, a different issue, or irrelevant, but I spotted this in the cache (I think it relates to the TMS API cache I/O):

The .../DEFAULT/DEFAULT.... is weird...

Expected Behavior

• The typology processor must deliver its completed results to the TADProc.
• The Typology processor must properly com,piled the cacheKey for interacting with Valkey.