Warn on module replacement in `add_composable_module`

I've hit a surprising behavior by accidentally adding same module twice. I think it will be more fail proof to inform user that module is being replaced, invalidating everything that depends on it. It should probably be an error to add the same module twice, but since I'm not sure whether current behavior is desirable I left it as is.