[Issue 10202][pulsar-broker] Update the authentication data when an authentication refresh happens

[kaushik-develop]

Fixes #10202

Motivation

A pulsar broker does not refresh authentication data when an authentication state completes and a refresh happens. This change is to fix the issue.
Without this fix, the server can be seen to continue using stale auth data.

Modifications

• Use the new authData when an authentication state changes to "complete"
• In the producer/consumer classes, do not cache the authData; get it from the connection

Verifying this change

• Make sure that the change passes the CI checks.

This change added tests and can be verified as follows:

• Added an integration test [testExpiringTokenWithRefreshAndProducerRestart()] to verify

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: don't know

Documentation

• Does this pull request introduce a new feature? no
• If yes, how is the feature documented? not applicable
• If a feature is not applicable for documentation, explain why?
• If a feature is not documented yet in this PR, please create a followup issue for adding the documentation

[hsaputra]

LGTM +1

[kaushik-develop]

/pulsarbot run-failure-checks

[kaushik-develop]

/pulsarbot run-failure-checks

[kaushik-develop]

/pulsarbot run-failure-checks