fix: meet scope mapping and reply QP soft-wrap corruption

[shigechika]

Summary

• fix(auth): gws auth login -s meet が Meet スコープを1件も要求しない問題を修正。map_service_to_scope_prefixes に "meet" => vec!["meetings"] を追加。upstream PR fix(auth): map meet service to meetings scope prefix googleworkspace/cli#754 に相当。
• fix(gmail): +reply プレーンテキストモードで、元メールの本文が70〜75文字付近でハードラップされていると、> プレフィックス付加後に76文字を超えた行が Quoted-Printable のソフトラップ (=\r\n) を引き起こし、引用テキスト中に > が挿入されて文章が崩れるバグを修正。format_quoted_original でプレフィックス付加前に73文字でプリラップするよう修正。upstream issue +reply (plain text) corrupts quoted parent when hard-wrapped lines push prefixed lines past 76 chars googleworkspace/cli#769 に相当。

Test plan

• cargo clippy -- -D warnings — 警告なし
• cargo test — 826テスト全通過
• 追加テスト: scope_matches_service_meet (auth)
• 追加テスト: test_format_quoted_original_long_lines_do_not_exceed_75_chars, test_word_wrap_preserves_short_lines, test_word_wrap_breaks_long_line (reply)

References

• upstream PR fix(auth): map meet service to meetings scope prefix googleworkspace/cli#754: fix(auth): map meet service to meetings scope prefix
• upstream issue +reply (plain text) corrupts quoted parent when hard-wrapped lines push prefixed lines past 76 chars googleworkspace/cli#769: +reply (plain text) corrupts quoted parent when hard-wrapped lines push prefixed lines past 76 chars

🤖 Generated with Claude Code

[shigechika]

Splitting into separate PRs. reply.rs QP wrap fix is dropped — non-ASCII byte-length handling is a rabbit hole best left for a dedicated fix.