Hmm, this might be a bit trickier than I originally thought. The TinCanAPI can be enabled on a tenant-by-tenant basis. The routed activities however, are not emitted based on the tenant they originated from, so we kinda have to iterate over them.

We can do the following however:
 * Don't add the listener if none of the tenants has it enabled and listen for config changes to add it in when a tenant admin does
 * That loop in `_processActivities` can be optimized a bit so we're not transforming activities in LRS Statements when the originating tenant doesn't have it enabled.

I'm going to outscope that for this PR though