Minimal permissions for 'teams team' 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 team add
• m365 teams team archive
• m365 teams team clone
• m365 teams team get
• m365 teams team list
• m365 teams team remove
• m365 teams team set
• m365 teams team unarchive

Read the linked guidance on writing docs and documenting minimal permissions, then review the Planner examples for the expected Permissions section. Update the documentation for all eight listed teams team commands, placing the section before Examples and ordering multiple resources alphabetically. Done means each command documents its minimal delegated and application permissions, including auth-specific examples where applicable.