💡 [Feature]: Add get_spo_page Language Model Tool for modern SharePoint page information retrieval operation

[Saurabh7019]

🎯 Aim of the feature

Create a new Language Model Tool for retrieving SharePoint page information using the CLI for Microsoft 365 spo page get command.

Tool Specification

Name: get_spo_page Model description: The tool description must cover the following guidance:

• What exactly does the tool do? - describe the specific functionality and capabilities
• What kind of information does it return? - detail the expected response format
• When should and shouldn't it be used? - provide clear use cases and scenarios to avoid
• Describe important limitations or constraints of the tool - identify technical and permission limitations

Under the hood use: spo page get

The issue https://github.com/pnp/vscode-viva/issues/586 has been implemented and can be used as a reference to ensure consistency with the correct standards.

📷 Images (if possible) with expected result

No response

🤔 Additional remarks or comments

• VS Code LM docs: https://code.visualstudio.com/api/extension-guides/tools
• CLI for Microsoft 365 Reference: https://pnp.github.io/cli-microsoft365/cmd/spo/page/page-get

[Adam-it]

I think it's only worth mentioning that the new code should follow the same approach as we have for already existing LM Tool that allows to add a page. https://github.com/pnp/vscode-viva/blob/main/src/chat/tools/spo/PageAdd.ts Also, IMO we should put this onhold until #586 is done. That way we may ensure whoever will be implementing this LM tool will follow the new standard as well