unit-test: allow non-shell scripts for extensions
unit-test: allow non-shell scripts for extensions

The unit-test script currently allows extension scripts of the
name 'run-ci.sh', but there are examples within openbmc where
the extensions are not actually shell (at least one is Python).

Remove the extension requirement on the script by looking both
for 'run-ci.sh' and 'run-ci'.

Tested the 'find_file' script with:

    > find_file('run-ci', '.../openbmc-sources')
    ['.../openbmc-sources/phosphor-dbus-interfaces/run-ci']

    > find_file('run-ci.sh', '.../openbmc-sources')
    ['.../openbmc-sources/phosphor-logging/extensions/openpower-pels/registry/run-ci.sh',
     '.../openbmc-sources/phosphor-power/phosphor-regulators/test/run-ci.sh',
     '.../openbmc-sources/entity-manager/scripts/run-ci.sh' ]

    > find_file(['run-ci', 'run-ci.sh'], '.../openbmc-sources')
    ['.../openbmc-sources/phosphor-dbus-interfaces/run-ci',
     '.../openbmc-sources/phosphor-logging/extensions/openpower-pels/registry/run-ci.sh',
     '.../openbmc-sources/phosphor-power/phosphor-regulators/test/run-ci.sh',
     '.../openbmc-sources/entity-manager/scripts/run-ci.sh']

Signed-off-by: Patrick Williams <cbb7353e6d953ef360baf960c122346276c6e320@stwcx.xyz>
Change-Id: Ib420c69e88e88ca0a50863c83ad43fac750d3e7a

openbmc/openbmc-build-scripts,openbmc/openbmc-build-scripts