Fix bug for default numEvents in trigbs_updateBSMetadata.py

Fix bug I introduced in !35443 (merged) when adding the new option --numEvents. When the option is not specified, nmax becomes -1 and this should mean "process all events" but the check for negative nmax was actually missing from the loop over events. As a result, without --numEvents by default no events were written out instead of all.