Make workflow binaries broken

[ae9is]

GitHub Actions workflow for building binaries via Nuitka works for nuitka-test-simple but fails for nuitka-test-advanced and ezsam/gui/app.py throwing: ModuleNotFoundError: No module named 'ezsam'

[ae9is]

Nuitka/Nuitka-Action@main options:
https://github.com/ae9is/ezsam/blob/3be7aa03ccd880d309a8c6ec22590219dced7018/.github/workflows/make.yml#L57C1-L68C61

  - name: Build executable with Nuitka
    uses: Nuitka/Nuitka-Action@main
    with:
      # ref: https://github.com/Nuitka/Nuitka-Action/blob/main/action.yml
      nuitka-version: main
      enable-plugins: tk-inter
      onefile: true
      onefile-tempdir-spec: '{TEMP}/${{ github.event.inputs.name }}'
      include-data-dir: ${{ github.event.inputs.datadir }}=${{ github.event.inputs.datadir }}
      product-name: ${{ github.event.inputs.name }}
      product-version: ${{ github.event.inputs.version }}
      file-version: ${{ github.event.inputs.version }}
      file-description: ${{ github.event.inputs.description }}
      output-dir: dist
      script-name: ${{ github.event.inputs.scriptname }}

Local builds with Nuitka work fine (via make-nuitka.sh).

Local build script command:

assets="src/ezsam/gui/assets"
description='ezsam is a tool to extract objects from images or video via text prompt - info at https://www.ezsam.org'
dist="dist-nuitka"
tempdir="{TEMP}/ezsam"
outfile="${name}-${version}.bin"
echo "Creating ${name}-${version} at `date` ..."
python -m nuitka --enable-plugin=tk-inter --onefile \
  --onefile-tempdir-spec="${tempdir}" \
  --include-data-dir="${assets}=${assets}" \
  --output-filename="${outfile}" \
  --product-version="${version}" \
  --file-version="${version}" \
  --file-description="${description}" \
  --output-dir="${dist}" "${entrypoint}"

[ae9is]

The differences between the two are due to options for Nuitka-Action:

1. script-name instead of input argument, but they should be the same
2. output-filename is not a valid parameter in the action, because it's designed to generate executables for multiple platforms at once and so adds a platform specific suffix. Instead, product-name is used to set the embedded name in the executable and the workflow renames the executable later. product-name in the local script defaults to the output-filename's basename, so it is not set locally.