Fix devcontainer CI base-image resolution in Build and scan jobs

[Copilot]

Build and scan (amd64) failed during the Build Dev Container step because devcontainers/ci attempted to resolve ghcr.io/owasp/wrongsecrets-devcontainer:26-resolute-base from GHCR instead of using the locally tagged base image. This change aligns builder selection so the local base tag is resolvable in workflow execution.

• Root cause

  • devcontainers/ci was not using the intended Buildx context for consuming the locally tagged base image (26-resolute-base), causing remote lookup failures (not found).

• Workflow change

  • Updated .github/workflows/build-devcontainer.yml in the Build Dev Container step to pin the builder context used by devcontainers/ci.

• Why this unblocks the job

  • Ensures the devcontainer build can consume the locally produced/tagged base image before scan/publish stages proceed.

- name: Build Dev Container
  uses: devcontainers/ci@v0.3
  env:
    BUILDX_BUILDER: default
  with:
    imageName: devcontainer-${{ matrix.arch }}-${{ github.sha }}
    push: never

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.