fix(auth): add People and Meet scopes to login picker

[anshul-garg27]

Summary

gws auth login didn't offer scopes for People API or Meet API in the interactive picker, so users got insufficient authentication scopes errors when calling gws people or gws meet commands.

• Add contacts (People API) and meetings.space.created (Meet API) to the TUI scope picker
• Include both in FULL_SCOPES so --full covers them
• Map meet service name to meetings scope prefix so -s meet filters correctly

Closes #556

Test plan

• cargo test — 750 pass, 0 fail
• cargo clippy -- -D warnings — clean
• New test: scope_matches_service_meet_meetings verifies the mapping

[changeset-bot]

🦋 Changeset detected

Latest commit: 1fa1bd0

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@googleworkspace/cli	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the authentication process by integrating previously missing scopes for the Google People and Meet APIs. This ensures that users can successfully authenticate and utilize gws people and gws meet commands without encountering scope-related errors. The changes involve updating scope definitions, the interactive picker, and service-to-scope mapping, along with a new test to validate the functionality.

Highlights

• Authentication Scopes: Added Google People API (contacts) and Google Meet API (meetings.space.created) scopes to the interactive login picker, resolving 'insufficient authentication scopes' errors.
• Full Scope Preset: Included the newly added People and Meet API scopes in the FULL_SCOPES constant, ensuring they are covered by the --full authentication option.
• Service Mapping: Implemented a mapping for the meet service name to the meetings scope prefix, allowing correct filtering when using -s meet.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

1. Review the Generative AI Prohibited Use Policy, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request adds the necessary scopes for the Google People and Meet APIs to fix insufficient authentication scopes errors. The changes update FULL_SCOPES, the interactive scope picker, and add a service mapping for meet. A new test verifies this mapping. The implementation correctly addresses the described issue.