tidb-binlog: Add RESOLVED as a new binlog type

[suzaku]

What problem does this PR solve?

There's no easy way to differenciate a message containing resolved
timestamp and one that is ordinary binlog.

By adding RESOLVED as a BinlogType and reuse the commit_ts field
for resolved_ts, the consumer can just decode all message as usual and
look out for RESOLVED binlogs.

What is changed and how it works?

1. Add a third BinlogType: RESOLVED
2. Regenerate the go file.

Check List

Tests

• No code

Code changes

Side effects

Related changes

[july2993]

just use your own branch to dev first

[suzaku]

just use your own branch to dev first

👌

[IANTHEREAL]

LGTM

[IANTHEREAL]

@july2993 PTAL

[july2993]

lgtm

[IANTHEREAL]

/run-all-tests

[ti-chi-bot]

@suzaku: PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
0 out of 2 committers have signed the CLA.

❌ suzaku
❌ IANTHEREAL
_{You have signed the CLA already but the status is still pending? Let us recheck it.}