Backport PR #17124 to 9.0: plugin manager: add --no-expand flag for list command

[github-actions]

Backport PR #17124 to 9.0 branch, original message:

---

Release notes

• The plugin manager bin/logstash-plugin's list command now supports a --no-expand flag to avoid expanding plugin aliases and the individual plugins within integration plugins.

What does this PR do?

Adds --[no-]expand flag (default: true) to the plugin manager's list command, so that a caller can avoid expanding the integration plugins and aliases to get only a list of the plugin packages installed.

Why is it important/What is the impact to the user?

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation
• [] I have made corresponding change to the default configuration files (and/or docker env variables)
• I have added tests that prove my fix is effective or that my feature works

Author's Checklist

• file doc issue

How to test this PR locally

bin/logstash-plugin list --no-expand

bin/logstash-plugin list --verbose --no-expand

bin/logstash-plugin list --no-expand logstash-integration-aws

bin/logstash-plugin list --no-expand --verbose logstash-integration-aws

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 5c8888c

Failed CI Steps

• 🥼 IT Persistent Queues / part 1

[yaauie]

Closing without merging, as this is a feature and 9.0 is past feature freeze.