logger names bug

[keara-soloway]

In this pipeline:

- common.NexusReader:
    filename: data.nxs
    nxpath: structured_data
- common.PrintProcessor

The logger for the common.NexusReader somehow ends up named common.PrintProcessor which leads to confusing log statements like

...
2026-04-06 08:29:39: Pipeline            : INFO: Calling "execute" on NexusReader
2026-04-06 08:29:39: common.PrintProcessor: DEBUG: Executing "read" with schema "None" and {}
2026-04-06 08:29:39: common.PrintProcessor: INFO: Executing "read"
2026-04-06 08:29:39: common.PrintProcessor: INFO: Finished "<bound method NexusReader.read of NexusReader(root=PosixPath('<BLAH>'), inputdir=PosixPath('/<BLAH>'), outputdir=PosixPath('<BLAH>'), interactive=False, log_level='DEBUG', logger=<Logger common.PrintProcessor (DEBUG)>, name='NexusReader', schema_=None, filename='<BLAH>/data.nxs', nxpath='structured_data', idx=None, mode='r', nxmemory=None)>" in 0 seconds
...

[keara-soloway]

I think the general case is: any item immediate preceding a PrintProcessor has the (usually incorrect) logger name common.PrintProcessor.