[copy_from] support an optional INTO keyword, i.e. COPY (INTO)? <table> FROM

[ParkMyCar]

Chatted about this in the rnd-sql-council. This PR adds support for an optional INTO keyword for COPY ... FROM.

Motivation

Other databases use the syntax of COPY INTO <table> FROM ... and IMO makes the statement easier to understand for folks that are unfamiliar.

Checklist

• This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
• This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
• If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
• If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).
• If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.