[next] nilrt-snac: make test output ptest-compliant

[amstewart]

The NI ptest-parser (and ptests in general) use the AutoMake style of test output. The nilrt-snac integration tests uses pytest formatting, which is generally non-compliant and obscures individual testcase output from being parsed by the RTOS ptesting pipeline.

Use the python3-unittest-automake-output plugin for pytest, to output the test results in format ptest can parse.

AB#2776057

Testing

• I have built the core package feed with this PR in place. (bitbake packagefeed-ni-core)
• Tested the new package on a real crio-904x series. New test output looks like this:

admin@NI-cRIO-9049-01CEEE05:/usr/lib/nilrt-snac/ptest# ptest-runner nilrt-snac
START: ptest-runner
2024-09-20T15:09
BEGIN: /usr/lib/nilrt-snac/ptest
PASS: test_cli.py:test_help
PASS: test_cli.py:test_noargs
PASS: test_cli.py:test_verify
PASS: test_cli.py:test_version
PASS: test_installation.py:test_conflicts_ipk
PASS: test_installation.py:test_iptables
PASS: test_installation.py:test_opkg_binary
PASS: test_installation.py:test_supported_distro
PASS: test_installation.py:test_wireguard_conf
============================================================================
Testsuite summary
# TOTAL: 9
# PASS: 9
# SKIP: 0
# XFAIL: 0
# FAIL: 0
# XPASS: 0
# ERROR: 0
DURATION: 4
END: /usr/lib/nilrt-snac/ptest
2024-09-20T15:09
STOP: ptest-runner
TOTAL: 1 FAIL: 0

Procedure

• I certify that the contents of this pull request complies with the Developer Certificate of Origin.

[amstewart]

Patch V2

• Fixed whitespace in ptest entrypoint.
• Added env PATH fixup so that the verify workflow can find the nirtcfg binary when running non-interactively.