[fix] Fix AoP can't work when enabling Pulsar transaction

[gaoran10]

Motivation

Currently, AoP can't read messages and deliver them when enabling Pulsar transaction, it's due to that the max read position didn't refresh after messages were published.

Modifications

Update max read position while messages are published.

Verifying this change

Add a test to verify that AoP works well when enabling Pulsar transaction.

Does this pull request potentially affect one of the following parts:

If yes was chosen, please highlight the changes

• Dependencies (does it add or upgrade a dependency): (no)
• The public API: (no)
• The schema: (no)
• The default values of configurations: (no)
• The wire protocol: (no)
• The rest endpoints: (no)
• The admin cli options: (no)
• Anything that affects deployment: (no)

Documentation

Check the box below.

Need to update docs?

• doc-required

  (If you need help on updating docs, create a doc issue)

• no-need-doc

  (Please explain why)

• doc

  (If this PR contains doc changes)

[GhostBoyBoy]

Do multiple bundle scenarios require testing?

[gaoran10]

Do multiple bundle scenarios require testing?

I think the multi-bundle case doesn't have this problem, because when enabling the multi-bundle messages will be published by producers, I'll have a try.

[gaoran10]

@GhostBoyBoy I enable transactions in tests, the multi-bundle test will also apply this change.