Support configuring AWS configuration values on SpinApp for SQS triggered apps

The Spin SQS Trigger expects the following AWS configuration variables to be set in the environment at start up:

• AWS_DEFAULT_REGION
• AWS_ACCESS_KEY_ID
• AWS_SECRET_ACCESS_KEY
• AWS_SESSION_TOKEN

We could support configuring these by updating the SpinApp CRD to contain an sqs section:

spec:
  createDeployment: true
  deploymentConfig:
    runtimeClassName: wasmtime-spin-v2
    sqs:
      - aws_default_region: us-west-2
      - aws_secret_access_key:
            valueFrom:
              secretKeyRef:
                name: "my-super-secret"
                key: "turso-token"

Alternatively, the trigger could be updated to get these values from runtime config instead: https://github.com/fermyon/spin-trigger-sqs/issues/52

Start by reviewing the SpinApp CRD and the Spin SQS Trigger issue linked in the description. Decide whether AWS values belong in the CRD or runtime configuration, then verify that all four variables, including SecretKeyRef-based values, reach SQS-triggered deployments. Done means the chosen configuration path is documented and tested for deployment.