Google-only example workflow uses unsupported action inputs

Description

While testing the Google-only example workflow, GitHub Actions reports unsupported inputs for stackql-audit-action.

The workflow completes successfully, but the audit summary shows an empty project and 0 findings.

GitHub Actions reports the following warning:

Unexpected input(s) 'gcp-project-id', 'upload-logs', 'log-retention-days',
valid inputs are ['project-id', 'gcp-credentials', 'google-provider-version',
'queries-path', 'fail-on-severity', 'stackql-version']

Observed behavior

The workflow completes with Success, but the generated summary shows:

Project: ``
Checks run: 7
Errors: 0
Total findings: 0

The project value is empty even though a GCP project was configured for the workflow.

Expected behavior

The Google-only example workflow should use the currently supported action inputs so that the configured GCP project is passed correctly to the audit.

Based on the current action inputs, it looks like:

gcp-project-id:

should be:

project-id:

The example also passes:

upload-logs:
log-retention-days:

but these do not appear in the current list of supported action inputs.

Additional context

I found this while validating the Google-only audit workflow for a tutorial.

After using the supported project-id input, the audit was able to query the intended GCP project and return the expected findings.

Start with the Google-only example workflow and compare its stackql-audit-action inputs with the supported input list in the issue. Remove unsupported inputs and use project-id for the configured GCP project, then run the workflow and confirm the summary contains the project and expected findings.