Backport PR #17082 to 8.x branch, original message:

Release notes

[rn: skip]

What does this PR do?

Ensures that Logstash integration tests are run against a clean expansion of the built tarball.

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

Because QA tests can modify the Logstash installation (e.g. those that invoke the plugin manager), it is important that the service wrapper begins with a clean expansion of the logstash tarball.

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

How to test this PR locally

Run integration tests that invoke the Logstash service (or any of its sub-command features like the plugin manager):

ci/integration_tests.sh specs/cli/remove_spec.rb

Logs

see expunging, indicating that the old was removed
see expanding, indicating a fresh expansion
see Using...as LS_HOME, indicating that the fresh expansion is being used

    CLI > logstash-plugin remove
    expunging(/Users/rye/src/elastic/logstash@main/build/qa-fixture/logstash-9.1.0-SNAPSHOT)
    expanding(/Users/rye/src/elastic/logstash@main/build/logstash-9.1.0-SNAPSHOT.tar.gz)
    Using /Users/rye/src/elastic/logstash@main/build/qa-fixture/logstash-9.1.0-SNAPSHOT as LS_HOME
    Setting up services
    Setting up logstash service
    Setup script not found for logstash
    logstash service setup complete
      when other plugins depends on this plugin
        refuses to remove the plugin and display the plugin that depends on it.
      when no other plugins depends on this plugin
        successfully remove the plugin

    Finished in 2 minutes 0.2 seconds (files took 0.98941 seconds to load)
    2 examples, 0 failures