The test suite should include testing the filebeat binary.

The tests should include simply checking for the "filebeat" command so it is in the path and it can run on the architecture. This shows the binary file was delivered correctly and can be run. See the other beats tests for examples.

Start by locating the existing tests for other beats and the test entry point in this repository. Add a check that the filebeat command is available on PATH and can run on the target architecture, then run the relevant test suite to verify the delivered binary is executable.

Written by the indexing model from the issue text.