Fix FTR command line options for 7.17

[liza-mae]

There appears to be a bug on 7.17 branch for the following FTR options: --include and --exclude, see below:

On main:

    --include=file     a test file to be included, pass multiple times for multiple files
    --exclude=file     a test file to be excluded, pass multiple times for multiple files
    --include-tag=tag  a tag to be included, pass multiple times for multiple tags. Only
                         suites which have one of the passed include-tag tags will be executed.
                         When combined with the --exclude-tag flag both conditions must be met
                         for a suite to run.
    --exclude-tag=tag  a tag to be excluded, pass multiple times for multiple tags. Any suite
                         which has any of the exclude-tags will be excluded. When combined with
                         the --include-tag flag both conditions must be met for a suite to run.

On 7.17:

    --include-tag=tag  a tag to be included, pass multiple times for multiple tags. Only
                         suites which have one of the passed include-tag tags will be executed.
                         When combined with the --exclude-tag flag both conditions must be met
                         for a suite to run.
    --exclude-tag=tag  a tag to be excluded, pass multiple times for multiple tags. Any suite
                         which has any of the exclude-tags will be excluded. When combined with
                         the --include-tag flag both conditions must be met for a suite to run.
    --include-tag=tag  a tag to be included, pass multiple times for multiple tags
    --exclude-tag=tag  a tag to be excluded, pass multiple times for multiple tags

Although despite the help message, I pass in --exclude tag on 7.17 but it does not work.

Can we fix 7.17 for the --include and --exclude options?

cc: @spalger

[elasticmachine]

Pinging @elastic/kibana-operations (Team:Operations)

[liza-mae]

When can this be looked at?

[liza-mae]

Turns out this was an issue with the paths when running inside x-pack directory versus outside, the functionality appears to work, just the help message needs updating.

[Ikuni17]

Fixed by #157207