feat: migrate to pyproject.toml

[rinarakaki]

Tracking issue googleapis/google-cloud-python#13171

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 #<issue_number_goes_here> 🦕

[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/

[chalmerlowe]

LGTM

[chalmerlowe]

@rinarakaki

Thank you for your assistance with converting this to pyproject.toml.

I am curious... you went through and offered up conversion PRs for a large number of google projects. What inspired this?

[rinarakaki]

@chalmerlowe
Thanks for reviewing this PR!

For me, it was more about how to motivate/inspire the project maintainers to migrate to pyproject.toml, because this kind of problem (build systems) can only be solved in coordination with other projects, as they tend to rely on the common internal practices, standards and tooling. I use these libraries at work and want them to keep up with the latest Python standards and trends (including typing). pyproject.toml is a good first step towards modernising these Python projects, I believe.

[chalmerlowe]

@rinarakaki

That makes sense.
I manage:

• python-bigquery
• python-bigquery-pandas
• python-bigquery-sqlalchemy
• python-bigquery-storage
• python-db-dtypes-pandas

and will be migrating all of these to pyproject.toml in the near future.