Add more parameters for new billing on autocomplete and Place details - #241

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

I signed it!

CLAs look good, thanks!

This is already awaiting in #234.

Thanks all the same.

@stephenmcd Didn't see yours before but that's not exactly the same work.

• I let the choice to not use session_token with autocomplete.
• It's possible to use categories to set a list of fields without having to set them one by one.
• I used black to format the project.
• I added pipenv files to the project
• I don't raise exception if the developer use non existent fields. I think Exception should not be raise to do what the documentation does already. But that's my point of view
• There are no conflicts

I think our branchs could be merged as they have complementary features.

If you don't want to use my pull request, please fix and update #234

Regards,
Seb