Add support for subscription expiration time namespace settings

[klevy-toast]

Fixes #1253

Motivation

Adds support for the get / set / delete subscriptionExpirationTime namespace settings.

Modifications

Created new functions in namespace.go that implement support for subscriptionExpirationTime settings

Verifying this change

• Make sure that the change passes the CI checks.

  • Added integration tests for new client functions

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 / no)
• The schema: (yes / no / don't know)
• The default values of configurations: (yes / no)
• The wire protocol: (yes / no)

Documentation

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

[RobertIndie]

LGTM. Please fix the conflict

[klevy-toast]

Thanks for the review @RobertIndie , I have fixed the merge conflicts

[RobertIndie]

Please take a look at this compilation error: https://github.com/apache/pulsar-client-go/actions/runs/10045685387/job/27779892242?pr=1254#step:5:30

  Error: pulsaradmin/pkg/admin/namespace_test.go:234:11: undefined: admin

@klevy-toast

[klevy-toast]

Thanks, fixed @RobertIndie

[RobertIndie]

There are still some lint issues. If you are using macos or linux, you can run make lint to check locally.

[klevy-toast]

@RobertIndie thanks, fixed.

Is there a way for me to run the build independently? It's a bit annoying that I cannot see what issues are failing the build until a maintainer triggers it.

[RobertIndie]

Is there a way for me to run the build independently? It's a bit annoying that I cannot see what issues are failing the build until a maintainer triggers it.

You can run make build to build it locally. To check for CI failures, you can open a pull request in your own repository. This allows you to review any CI issues directly.

[klevy-toast]

Is there a way for me to run the build independently? It's a bit annoying that I cannot see what issues are failing the build until a maintainer triggers it.

You can run make build to build it locally. To check for CI failures, you can open a pull request in your own repository. This allows you to review any CI issues directly.

That's great info, can it be added to the contributing guide?