FIX: [CORE REGISTRY CADT] Logger appears to not be piping all logs correctly to the proper app

[ccornick]

Zach from the following logs when running Core Registry API

Feb 29 19:26:23 ip-10-102-2-47 core-registry-api[1410277]: 2024-02-29 19:26:23 [1.7.6] [info]: Getting confirmation for 1019153f631bb82e7fc4984dc1f0f2af9e95a7c29df743f7b4dcc2b975857409.
Feb 29 19:26:23 ip-10-102-2-47 core-registry-api[1410277]: [cadt] 2024-02-29 19:26:23 [1.7.6] [info]: Store found in DataLayer: 1019153f631bb82e7fc4984dc1f0f2af9e95a7c29df743f7b4dcc2b975857409.
Feb 29 19:26:23 ip-10-102-2-47 core-registry-api[1410277]: [cadt] 2024-02-29 19:26:23 [1.7.6] [debug]: Store is confirmed, proceeding to get data 1019153f631bb82e7fc4984dc1f0f2af9e95a7c29df743f7b4dcc2b975857409
Feb 29 19:26:23 ip-10-102-2-47 core-registry-api[1410277]: [cadt] 2024-02-29 19:26:23 [1.7.6] [info]: Downloaded Data, root hash: latest
Feb 29 19:26:23 ip-10-102-2-47 core-registry-api[1410277]: [cadt] 2024-02-29 19:26:23 [1.7.6] [info]: Subscription Found for 18b6ff2ebf73574d30a39e1ee58efa3b7e8f1b35a4f9e6abd41690ab87bd15c7.
Feb 29 19:26:23 ip-10-102-2-47 core-registry-api[1410277]: [cadt] 2024-02-29 19:26:23 [1.7.6] [info]: Getting confirmation for 18b6ff2ebf73574d30a39e1ee58efa3b7e8f1b35a4f9e6abd41690ab87bd15c7.

Note how some logs have [CADT] and others dont. Explore why this is happening.