Calls in the export process that don't trigger logging

[samuelbray32]

Describe the bug In testing the export and docker pipeline, found several cases where entries weren't logged for the SQL dump that we should probably include or make clear in documentation wont be hit. Listing here:

Using a table to restrict another

• There were cases in my code where I select entries in table1 via table1 & (table2 & key) or table1 * (table2 & key)
• Since i never fetch from table2 it doesn't get exported. This then changes behavior of the restriction in the docker
• This could also be solved on the user end by ensuring call made as table1 & (table2 & key).fetch("KEY")

fetch_nwb

• calling fetch_nwb from the merge table did not register the merge table entries in the export.
• The entries of the parent source table were registered
• Call in the code tracked for export: (LFPOutput & basic_key).fetch_nwb(restriction=basic_key)[0]["lfp"] where basic_key has restrictions for the source table LFPV1()