feat(geo): add support for geography

[steffnay]

Trying to locate which portions of code need to be touched. tests totally failing!
Just seeking feedback on how this should actually be done.

• Tests and linter pass
• Code coverage does not decrease (if any source code was changed)
• Appropriate docs were updated (if necessary)

[stephenplusplus]

It looks like the lint task is being a bit faily. You could try running npm run fix to sort out the issues and then see if there are any issues left. 🤞

> @google-cloud/[email protected] posttest /tmpfs/src/github/nodejs-bigquery
> npm run check
> @google-cloud/[email protected] check /tmpfs/src/github/nodejs-bigquery
> gts check
/tmpfs/src/github/nodejs-bigquery/system-test/bigquery.ts
  Lines: 1309-1321
          table = dataset.table(generateName('table'));
          return table.create({
            schema: [
   -          'date:DATE',
   -          'datetime:DATETIME',
   -          'time:TIME',
   -          'timestamp:TIMESTAMP',
   -          'numeric:NUMERIC',
   -          'geography:GEOGRAPHY'
   +          'date:DATE', 'datetime:DATETIME', 'time:TIME', 'timestamp:TIMESTAMP',
   +          'numeric:NUMERIC', 'geography:GEOGRAPHY'
            ].join(', '),
          });
        });
clang-format reported errors... run `gts fix` to address.

- Build log

[callmehiphop]

We should add some tests to the SQL Parameter system-tests.

[JustinBeckwith]

LGTM, assuming callmehiphop signs off

[callmehiphop]

Looks good, I think all we're missing are some tests. We should make sure that we can

• use Geography as a SQL Parameter
• unit test that GEOGRAPHY returns a Geography object.

[codecov]

Codecov Report

Merging #397 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #397      +/-   ##
==========================================
+ Coverage   99.45%   99.46%   +<.01%     
==========================================
  Files           4        4              
  Lines         550      556       +6     
  Branches       76       76              
==========================================
+ Hits          547      553       +6     
  Misses          2        2              
  Partials        1        1

Impacted Files	Coverage Δ
src/table.ts	100% <ø> (ø)	⬆️
src/index.ts	98.59% <100%> (+0.04%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 355d4d9...89aca53. Read the comment docs.

[googlebot]

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of all the commit author(s), set the cla label to yes (if enabled on your project), and then merge this pull request when appropriate.

ℹ️ Googlers: Go here for more info.

[googlebot]

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

ℹ️ Googlers: Go here for more info.

[googlebot]

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of all the commit author(s), set the cla label to yes (if enabled on your project), and then merge this pull request when appropriate.

ℹ️ Googlers: Go here for more info.

[JustinBeckwith]

LGTM assuming no new skipped tests are added

[googlebot]

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

ℹ️ Googlers: Go here for more info.

[googlebot]

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of all the commit author(s), set the cla label to yes (if enabled on your project), and then merge this pull request when appropriate.

ℹ️ Googlers: Go here for more info.

[callmehiphop]

@JustinBeckwith @jkwlui can one of you please defeat the cursed cla 🤖 megaboss?

[googlebot]

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

ℹ️ Googlers: Go here for more info.

[JustinBeckwith]

🎉