Minimal permissions for 'spo navigation node' 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 spo navigation node add
• m365 spo navigation node get
• m365 spo navigation node list
• m365 spo navigation node remove
• m365 spo navigation node set

Start with the Writing the docs page and the minimal-permissions guide, then open the documentation pages for m365 spo navigation node add, get, list, remove, and set. Add a Permissions section before Examples on each page, documenting the minimal delegated and application permissions, alphabetizing multiple resources and noting auth-type limitations where applicable.