Support to avoid circular fetching for PostgreSQL by pgoutput pulgin. [DBZ-3805]

Migrated from [DBZ-3805](https://issues.redhat.com/browse/DBZ-3805)

# Question

Postgres connector not support capture the data that is just "write" to this db, except for the replicated data. so that If there are two bidirectional copies of DB, Debezium will capture a lot of useless data.

# Solution

As per the specification of the [Logical Replication Message Format](https://www.postgresql.org/docs/12/protocol-logicalrep-message-formats.html), the pgoutput plugin supports the 'Origin' message type to record the data origin name, for instance in the case of multi-master set-ups. So, if we come across this field and find that the source is something we want to avoid copying, we can skip it until we hit 'Commit'.

Another approach is to put the Origin name field in the message body and let the user decide whether the messages are processed or not.

Start by reading the PostgreSQL Logical Replication Message Format specification linked in the issue, focusing on the pgoutput Origin message and transaction boundaries. Determine whether the intended behavior is filtering origins before Commit or exposing the origin for user decisions; the issue does not identify files, tests, or a final acceptance condition.

Written by the indexing model from the issue text.