Unable to deploy Timestream scheduled query when querying an empty table

### Name of the resource

AWS::Timestream::ScheduledQuery

### Resource name

_No response_

### Description

Attempting to deploy a ScheduledQuery that queries an empty table results in an exception:

```
ScheduledQuery: Resource handler returned message: "line 12:25: Column 'foo' does not exist (Service: AmazonTimestreamQuery; Status Code: 400; Error Code: ValidationException; Request ID: OSQH3TTQWMV4BP6W7NKAZS324M; Proxy: null)" (RequestToken: a86574da-20c5-0081-1c7f-05eae4b55b2f, HandlerErrorCode: InvalidRequest)
```

It would be nice if this were a warning instead of an error, or if the construct could be deployed but execution deferred until the validation passes. The current behavior makes deployment of tiered scheduled queries especially inconvenient.

### Other Details

_No response_

Start by reproducing deployment of AWS::Timestream::ScheduledQuery against an empty table and review the reported AmazonTimestreamQuery ValidationException. No repository files or tests are named in the issue, so first locate the coverage or resource-handling entry point for this resource. Done means establishing whether deployment can safely warn or defer validation without breaking scheduled-query execution.

Written by the indexing model from the issue text.