Mysqlbinlog with unknown GTID start position outputs events from wrong server id

When a given GTID --start-position is invalid (can't find a corresponding event that matches the given domain_id-server_id-seq_no), mysqlbinlog will output any events after it finds one greater than the given seq_no for a domain. It should wait until it also matches against server id, as this is how the replica behaves. Specifically, mysqlbinlog should only output events after finding one that is both 1) greater than the given seq_no for the domain, and 2) equal to the provided server id.