fix: app smoke test failing due to required login

[MichaelGoberling]

No description provided.

[MichaelGoberling]

App plugin is now outputting web action urls that point to the deploy service -> https://github.com/adobe/aio-e2e-tests/actions/runs/15535392853/job/43733091670#step:11:14

I think in this case we still want them to be adobeio-static urls

[MichaelGoberling]

Successful run: https://github.com/adobe/aio-e2e-tests/actions/runs/15688267263/job/44196848222

[Copilot]

Pull Request Overview

This PR adds an authentication step to the app smoke test workflow so that subsequent commands run with a valid Adobe IO login.

• Insert a new “Auth” step using adobe/aio-apps-action@3.3.0 configured via JWT secrets
• Ensures the smoke test won’t fail due to missing login

Comments suppressed due to low confidence (3)

.github/workflows/app-smoke-test.yml:39

• Add an explicit id: auth to this step so it’s easy to reference its outputs or status in later steps.

    - name: Auth

.github/workflows/app-smoke-test.yml:44

• Verify that the action expects CLIENTID in uppercase; many actions use camelCase (e.g., clientId)—mismatched casing could cause an authentication failure.

        CLIENTID: ${{ secrets.JWT_CLIENTID }}

.github/workflows/app-smoke-test.yml:48

• [nitpick] The input name KEY is very generic. If the action supports it, consider using PRIVATE_KEY or jwtPrivateKey to more clearly convey its purpose.

        KEY: ${{ secrets.JWT_PRIVATE_KEY }}