SRE-3827 test: assuming fault injection is enabled by default

[janekmi]

If the fault_status executable is not available (e.g. on a light agent where DAOS is not installed) we cannot rule out there are tests to run. It does not change the behaviour when fault_status is available so no more tests will get run but less stages will get skipped without good reason when the test scope is restricted allowing to run a single fault injection test if necessary.

Fault injection test below picked arbitrarily.

Test-tag: test_daos_pipeline

Skip-unit-tests:true
Skip-NLT: true
Skip-unit-test-memcheck: true
Skip-func-vm: true
Skip-fault-injection-test: true
Skip-test-rpms: true

Steps for the author:

• Commit message follows the guidelines.
• Appropriate Features or Test-tag pragmas were used.
• Appropriate Functional Test Stages were run.
• At least two positive code reviews including at least one code owner from each category referenced in the PR.
• Testing is complete. If necessary, forced-landing label added and a reason added in a comment.

After all prior steps are complete:

• Gatekeeper requested (daos-gatekeeper added as a reviewer).

[github-actions]

Errors are Unable to load ticket data
https://daosio.atlassian.net/browse/SRE-3827

[daltonbohning]

Seems reasonable to me, though I'll let @phender comment if there is something this might interfere with.

[grom72]

Please extend description with most common usecase:

If the fault_status executable is not available (for example on the test agent)
we cannot rule out there are tests to run. It does not change the behaviour when
fault_status is available so no more tests will get run but less stages
will get skipped without good reason when the test scope is restricted
allowing to run a single fault injection test if necessary.

[grom72]

@daos-stack/daos-gatekeeper please include in the final commit message the (e.g. on a light agent where DAOS is not installed) note