Minimal permissions for 'teams tab' 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 tab add
• m365 teams tab get
• m365 teams tab list
• m365 teams tab remove

Start with the documentation pages for m365 teams tab add, get, list, and remove, using the writing-the-docs and minimal-permissions guides linked in the issue. Add a Permissions section before Examples for each command, documenting the minimal delegated and application permissions and ordering multiple resources alphabetically. Done when all four pages follow the stated format and account for auth modes.