remove pulsar-standalone image

[freeznet]

Motivation

Currently, the pulsar-dashboard has been removed in #11284, as the pulsar-standalone image is required pulsar-dashboard and provide dashboard service in one container, which leads to building failure in pulsar-standalone image.

in #11623, as @merlimat suggests, this PR removes the pulsar-standalone image from master.

I did a quick search in the codebase to find if there is any doc related to pulsar-standalone image but seems no doc related to pulsar-standalone image anymore. so this PR will not include any doc changes.

Modifications

• remove pulsar-standalone image

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 / no)
• The schema: (yes / no / don't know)
• The default values of configurations: (yes / no)
• The wire protocol: (yes / no)
• The rest endpoints: (yes / no)
• The admin cli options: (yes / no)
• Anything that affects deployment: (yes / no / don't know)

Documentation

For contributor

For this PR, do we need to update docs?

• If yes, please update docs or create a follow-up issue if you need help.

• If no, please explain why.

For committer

For this PR, do we need to update docs?

• If yes,

  • if you update docs in this PR, label this PR with the doc label.

  • if you plan to update docs later, label this PR with the doc-required label.

  • if you need help on updating docs, create a follow-up issue with the doc-required label.

• If no, label this PR with the no-need-doc label and explain why.