💡 [Feature]: Update spo_list_get Language Model Tool to Follow standards

[Saurabh7019]

🎯 Aim of the feature

Refactor the existing spo_list_get Language Model Tool to align with updated naming conventions, improve model descriptions, and add additional list creation options for enhanced SharePoint list management capabilities.

Issues to address:

• Rename the tool to get_spo_list following the naming convention {verb}_{noun} as established in the codebase
• Improve modelDescription:
  • 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
• Refactor ListGet
  • Missing Properties: lets add support for the following options: withPermissions

Under the hood use: spo list get

The issue #586 has been implemented and can be used as a reference to ensure consistency with the correct standards.

🤖 Agent info

• create your feature branch with the implementation based on dev branch. This is a must
• when opening a PR you MUST target dev branch
• similar change was done in this commit 796856b. you must use it as refrence

🤔 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/list/list-get