Minimal permissions for 'teams chat related' commands

We're adding a new Permissions section to all commands. This section will document the minimal delegated and application permissions required to execute the command.

The goal is to:

• Make it easier to run the CLI with custom app registrations and application permissions.
• Ensure we only document the minimal set of permissions needed.
• Keep documentation consistent by placing the Permissions section right before the Examples section.
• If there are multiple resources, order them alphabetically
• If there are commands that only support one type of auth (like delegated or app-only), we have an example for that as well. E.g. m365 planner tenant settings list - Permissions

Resources

• Writing the docs page
• How to document minimal permissions
• Planner example 1
• Planner example 2

Commands in scope

This issue covers the following commands:

• m365 teams chat get
• m365 teams chat list
• m365 teams chat member add
• m365 teams chat member list
• m365 teams chat member remove
• m365 teams chat message list
• m365 teams chat message send

Start with the linked guides on writing docs and documenting minimal permissions, then review the seven listed Teams chat command documentation pages and compare the Planner examples. Add a Permissions section before Examples on each page, using minimal delegated or application permissions and alphabetizing multiple resources; completion means all seven pages follow the same format.