feat: re-exporting types for google-common

[loferris]

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

• Make sure to open an issue as a bug/issue before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
• Ensure the tests and linter pass
• Code coverage does not decrease (if any source code was changed)
• Appropriate docs were updated (if necessary)

Fixes #1268 🦕

This PR introduces a re-exporting pattern to the library that allows for users to import google-common along with bigquery. This option ensures that users' version of google-common is the same as the one used in the BigQuery library. This is also a way to gauge the value of re-exporting dependencies in the library.

[conventional-commit-lint-gcf]

🤖 I detect that the PR title and the commit message differ and there's only one commit. To use the PR title for the commit history, you can use Github's automerge feature with squashing, or use automerge label. Good luck human!

-- conventional-commit-lint bot
https://conventionalcommits.org/

[alvarowolfx]

Make sense to me. To we know if other libraries have that same kind of pattern ?

[loferris]

Make sense to me. To we know if other libraries have that same kind of pattern ?

I'm pretty sure the other languages do not, but it is a pattern in TypeScript libraries in general.