Create Fleet: panel implementation

[JunyuQian]

Description

This pull request introduces the basic panel implementation and required webview definitions for creating fleets in the VSCode extension.

Key Changes

1. Added Fleet Management Capabilities:

   • Introduced ContainerServiceFleetClient to manage AKS fleets.
   • Implemented getAksFleetClient function in arm.ts to create a fleet client.
   • Added CreateFleetPanel and CreateFleetDataProvider classes in CreateFleetPanel.ts for handling fleet creation UI and logic.

2. New Webview Definitions:

   • Created createFleet.ts under webviewDefinitions to define interfaces and message types related to fleet creation.
   • Updated webviewTypes.ts to include CreateFleetDefinition.

3. UI Enhancements:

   • Added placeholder for createFleet in main.tsx and manualTest/main.tsx to ensure compilation and future implementation. The code in main.tsx is hardcoded to satisfy dependencies for the project to compile.

Changes

• Files Modified:
  • src/commands/utils/arm.ts: Added ContainerServiceFleetClient and getAksFleetClient.
  • src/panels/CreateFleetPanel.ts: Created new panel and data provider for fleet creation.
  • src/webview-contract/webviewDefinitions/createFleet.ts: Defined types for fleet creation webview.
  • src/webview-contract/webviewTypes.ts: Added CreateFleetDefinition.
  • webview-ui/src/main.tsx: Added placeholder for fleet creation with hardcoded code to satisfy dependencies.
  • webview-ui/src/manualTest/main.tsx: Added placeholder for fleet creation test scenarios with hardcoded code to satisfy dependencies.

Testing

• Placeholder components have been added to ensure dependencies are resolved during compilation.
• Full implementation and test cases will be added in subsequent PRs.

Notes

• The right-click entry point for createFleet is not yet visible to users to avoid incomplete experience.
• The creation of resource groups is yet to be included.
• Test cases are yet to be added.

[tejhan]

Setup of everything LGTM !👍, would say some descriptive comments for some functions could help (Like for the validation criteria being used). I'm assuming the ProgressEventTypes are placeholders for now & could be modified in further PR's.

[Tatsinnit]

🐲 Thank you for this PR—this second part of the web view looks good to me! While it’s not yet connected, it’s clear that it’s heading in the right direction, and the U/X folks seem happy with it as well.

We’re now entering a crucial stage beyond this point, where connecting everything together will become key. I’d strongly encourage you to engage with Tejhan and Reinier pro-actively with the next PR, as it will likely be even more critical in tying everything together and ensuring success.

Once again, thank you for your efforts on this PR—it’s an important step forward. Feel free to reach out if there’s anything I can help with, or if more collaboration is needed as we move toward the next phase!

Humble thanks to everyone above for valuable comments.

• Once you cater left over comments, we can plan to squash, merge this mid-day today. 🤞 thanks.

[ReinierCC]

Looks good! Solid foundation so far.

As you start connecting things the next tricky part will be setting up the "state.ts" file which can be thought as the message/event handling on the webview side.

I'd recommend you try to load a simple "Hello World" before tackling the full fleet webview.

Feel free to reach out with any questions!

[JunyuQian]

Thank you all for your valuable comments!! I have carefully reviewed them and addressed all the issues in the latest commit :)