[BEAM-12482] Ensure that we ignore schema update options when loading temporary tables that don't exist.

[lukecwik]

Note that this doesn't solve schema update completely and only works if the destination table doesn't exist but expands slightly the set of use cases supported.

This depends on the destination table having a schema that matches that of the temp tables effectively making the SchemaUpdateOptions moot.

---

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

• Choose reviewer(s) and mention them in a comment (R: @username).
• Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
• Update CHANGES.md with noteworthy changes.
• If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

ValidatesRunner compliance status (on master branch)

Lang	ULR	Dataflow	Flink	Samza	Spark	Twister2
Go	---					---
Java
Python	---					---
XLang						---

Examples testing status on various runners

Lang	ULR	Dataflow	Flink	Samza	Spark	Twister2
Go	---	---	---	---	---	---	---
Java	---		---	---	---	---	---
Python	---	---	---	---	---	---	---
XLang	---	---	---	---	---	---	---

Post-Commit SDK/Transform Integration Tests Status (on master branch)

Go	Java	Python

Pre-Commit Tests Status (on master branch)

---	Java	Python	Go	Website	Whitespace	Typescript
Non-portable
Portable	---			---	---	---

See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

[lukecwik]

R: @chamikaramj
CC: @reuvenlax

[chamikaramj]

Do we need something similar to what was done for Python: #14113
(running a zero row load job against the destination table)

[lukecwik]

Do we need something similar to what was done for Python: #14113 (running a zero row load job against the destination table)

Yes. This is only a partial fix as in jobs that create the table will work and pushes the error further down the road as per the PR description.

[chamikaramj]

LGTM. Thanks.