Minimal permissions for 'teams user app' 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 user app add
• m365 teams user app list
• m365 teams user app remove
• m365 teams user app upgrade

Open the documentation pages for m365 teams user app add, list, remove, and upgrade, then read the linked guidance on writing docs and documenting minimal permissions. Add a Permissions section before Examples on each page, documenting only the required delegated and application permissions, with resources alphabetized and auth-specific examples where applicable.