timestamp_output_format is not supported yet. when running a query

### Please make sure you have searched for information in the following guides.

- [x] Search the issues already opened: https://github.com/GoogleCloudPlatform/google-cloud-node/issues
- [x] Search StackOverflow: http://stackoverflow.com/questions/tagged/google-cloud-platform+node.js
- [x] Check our Troubleshooting guide: https://github.com/googleapis/google-cloud-node/blob/main/docs/troubleshooting.md
- [x] Check our FAQ: https://github.com/googleapis/google-cloud-node/blob/main/docs/faq.md
- [x] Check our libraries HOW-TO: https://github.com/googleapis/gax-nodejs/blob/main/client-libraries.md
- [x] Check out our authentication guide: https://github.com/googleapis/google-auth-library-nodejs
- [x] Check out handwritten samples for many of our APIs: https://github.com/GoogleCloudPlatform/nodejs-docs-samples
- [x] Check the API's issue tracker: https://cloud.google.com/support/docs/issue-trackers

### Library Name

@google-cloud/bigquery

### A screenshot that you have tested with "Try this API".

There's an identical issue that was resolved in the go library https://github.com/googleapis/google-cloud-go/issues/13788.
I dug deep into the source with the debugger, and it seems that the library is attempting to use a feature that has not yet released in the api.
Here's the simplest query I could replicate in the api explorer. What's odd is that the explorer also suggests `timestampOutputFormat` as a valid option in the autocomplete. However, it doesn't seem to be released yet.

### Link to the code that reproduces this issue. A link to a **public** Github Repository or gist with a minimal reproduction.

https://gist.github.com/djohnson-aperture/1b16574011478dae9137aa1adca44210

### A step-by-step description of how to reproduce the issue, based on the linked reproduction.

Any basic query using `(new BigQuery()).query()` seems to have the same issue.
`(new BigQuery()).query('select 1;')` is enough to trigger the error.

### A clear and concise description of what the bug is, and what you expected to happen.

Any query throws a 400 error with the above mentioned error code.

### A clear and concise description WHY you expect this behavior, i.e., was it a recent change, there is documentation that points to this behavior, etc. **

I just expect a basic query to work...