fix: load packages whose run hook is a run file in the package root

[tas50]

The integration suites from #99 went green on library-package and red on default and user-toml, both of which load core/redis. The converge exited 0, and then the verifier found this:

ok: hab CLI installed: hab 1.6.1245/20250905140900
ok: hab-sup systemd unit written
ok: hab-sup service is running
ok: supervisor answers hab svc status
FAIL: core/redis was not loaded
--- hab svc status ---
No services loaded.

hab pkg install core/redis had succeeded a fraction of a second earlier. The load was never attempted.

Why

run_command gates the load on this:

if [ -f "$(sudo hab pkg path core/redis)/hooks/run" ]

The supervisor accepts a run hook in either of two places — hooks/run, written from a hook template, or a run file in the package root, which is what pkg_svc_run in a plan produces. We only ever checked the first.

core/redis is built the second way:

$ tar -tf core-redis-4.0.14-20240106065001-x86_64-linux.hart | grep -E '/(run|hooks/)'
hab/pkgs/core/redis/4.0.14/20240106065001/run

So for every package written that way — and pkg_svc_run is the older, simpler, still very common style, including the core/redis example in our own README — the provisioner installed the package, skipped the entire load branch, and reported success. No error, no warning, nothing in the output to suggest the service you asked for was never started.

The fix

Both platform paths now resolve the package path once and check both locations:

pkg_path="$(sudo hab pkg path core/redis)"
if [ -f "$pkg_path/hooks/run" ] || [ -f "$pkg_path/run" ]

$PkgPath = hab pkg path core/redis
if (@("hooks\run", "hooks\run.ps1", "run", "run.ps1") | Where-Object { Test-Path -Path (Join-Path $PkgPath $_) }) {

The Windows side also checks the .ps1 form of each, which is how a Windows plan spells the same two hooks.

library-package (core/jq-static, no run hook of either kind) keeps passing, so the negative branch is still covered — a library or build-time dependency still converges without a service being started.

Verification

$ bundle exec cookstyle --chefstyle
5 files inspected, no offenses detected

$ bundle exec rake test
152 examples, 0 failures
Line Coverage: 100.0% (226 / 226)
Branch Coverage: 92.74% (115 / 124)

The real check is this PR's own default and user-toml integration jobs, which should now go green.