fix: use continue-on-error for GitHub App auth instead of secrets check in if

The secrets context is not available during workflow_dispatch parsing,
causing a 422 error when triggering via API. Use continue-on-error
on the auth step and fall back to GITHUB_TOKEN in the token step.

Co-Authored-By: AJ Steers <aj@airbyte.io>

Author: devin-ai-integration[bot]

.github/workflows/generate-command.yml

@@ -66,9 +66,10 @@ jobs:
             pull-requests: write
         steps:
             - name: Authenticate as GitHub App
-              if: ${{ !inputs.dry_run && github.event.inputs.pr != '' && secrets.OCTAVIA_BOT_APP_ID != '' }}
+              if: ${{ !inputs.dry_run && github.event.inputs.pr != '' }}
               uses: actions/create-github-app-token@v3
               id: get-app-token
+              continue-on-error: true
               with:
                   app-id: ${{ secrets.OCTAVIA_BOT_APP_ID }}
                   private-key: ${{ secrets.OCTAVIA_BOT_PRIVATE_KEY }}
@@ -77,9 +78,9 @@ jobs:
               id: token
               run: |
                   if [ -n "${{ steps.get-app-token.outputs.token }}" ]; then
-                      echo "token=${{ steps.get-app-token.outputs.token }}" >> $GITHUB_OUTPUT
+                      echo "token=${{ steps.get-app-token.outputs.token }}" | tee -a $GITHUB_OUTPUT
                   else
-                      echo "token=${{ github.token }}" >> $GITHUB_OUTPUT
+                      echo "token=${{ github.token }}" | tee -a $GITHUB_OUTPUT
                   fi
 
             - name: Post or append starting comment