feat: add Bucket.reload() and Bucket.update() wrappers to restrict generation match args

[IlyaFaer]

Towards #127

[IlyaFaer]

@andrewsg, @frankyn, I've taken one more self review and found the thing, that got no our attention yet. We have only two if_metageneration* args in Bucket.reload() and Bucket.update() methods according to the design, and all four if_*generation* args in Blob.reload() and Blob.update() methods.

All of the above methods are inherited from _PropertyMixin class. I've added all four args into its methods, but that means user can pass if_generation_match arg into Bucket.reload(), which is not correct. More than that these args will be shown in docs, like they are okay to be passed:

I'm proposing to add wrapper methods into Bucket class to restrict if_generation* args, and keep only if_metageneration* ones.

[andrewsg]

Thanks for identifying this proactively!

[andrewsg]

LGTM but I'll pass this by Frank before merging just in case I'm missing something.

[gcf-merge-on-green]

Your PR has attempted to merge for 3 hours. Please check that all required checks have passed, you have an automerge label, and that all your reviewers have approved the PR

[gcf-merge-on-green]

Your PR has attempted to merge for 3 hours. Please check that all required checks have passed, you have an automerge label, and that all your reviewers have approved the PR

[gcf-merge-on-green]

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, or one of your required reviews was not approved. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.