[improve] PIP-368: Support lookup based on the lookup properties

[crossoverJie]

Motivation

Support pip: apache/pulsar#23223

Modifications

• Upgrade Pulsar image to 4.0.0
• Upgrade golint
• Client support LookupProperties

Verifying this change

• Make sure that the change passes the CI checks.

(Please pick either of the following options)

This change is a trivial rework / code cleanup without any test coverage.

(or)

This change is already covered by existing tests, such as (please describe tests).

(or)

This change added tests and can be verified as follows:

(example:)

• Added integration tests for end-to-end deployment with large payloads (10MB)
• Extended integration test for recovery after broker failure

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): (yes / no)
• The public API: (yes)
• The schema: (no)
• The default values of configurations: (no)
• The wire protocol: (yes)

Documentation

• Does this pull request introduce a new feature? (yes)
• If yes, how is the feature documented? (GoDocs)
• 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

[BewareMyPower]

Could you use a separated PR to fix conflicts after upgrading Pulsar to 4.0.0 like #1302?

BTW, I found the lint task in the Makefile is repeated, we use golangci/golangci-lint-action@v6 in CI, where make lint is never used.

[crossoverJie]

BTW, I found the lint task in the Makefile is repeated, we use golangci/golangci-lint-action@v6 in CI, where make lint is never used.

You are right, make lint can be used locally.

[BewareMyPower]

Could you use a separated PR to fix conflicts after upgrading Pulsar to 4.0.0?

In addition, we'd better use latest image by default.

[crossoverJie]

Could you use a separated PR to fix conflicts after upgrading Pulsar to 4.0.0?

Sorry, I didn't fully understand what you meant😂.

This PR has upgraded the image to 4.0.0. do you mean to create a separate PR for this part? I think the contents of this PR are not complicated, and the code review should be completed quickly.

[BewareMyPower]

This PR has upgraded the image to 4.0.0. do you mean to create a separate PR for this part?

Yes. Including the tool versions upgrade in a code PR is not a good practice.

[crossoverJie]

Yes. Including the tool versions upgrade in a code PR is not a good practice.

PTAL @BewareMyPower . #1304

[nodece]

LGTM, could you add a test for verify the lookup properties in the pulsar/internal/lookup_service_test.go?

[crossoverJie]

LGTM, could you add a test for verify the lookup properties in the pulsar/internal/lookup_service_test.go?

Relevant code has been added https://github.com/apache/pulsar-client-go/pull/1303/files#diff-eaa8996b10b63f4ccd290c3af5dff5397e3911ab7cd228e20ecc99f0d69aeff4.