feat: action create backend, organization, project, workspace

[hoangndst]

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

• N
• Y

fix #8

2. What is the scope of this PR (e.g. component or file name):

3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Other

4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

• N
• Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

• Unit test
• Integration test
• Benchmark (add benchmark stats below)
• Manual test (add detailed scripts or steps below)
• Other

6. Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[Yangyang96]

@hoangndst The latest version of @kusionstack/kusion-api-client-sdk - 1.1.5 now supports dual package formats (both ESM and CJS), which resolves the previous compilation issues.

I also have a few suggestions:

• Publicly publish the plugin to the kusionstack organization so that users can access it anywhere.
• Provide templates for these actions and configure them in app-config.yaml, allowing users to utilize them immediately.
• Correct the parameters for these actions, such as making backendID required for workspace and backend configs optional for backend. Please refer to the API documentation of Kusion 0.14.0 for guidance.

Thank you for your hard work! Great job! 🚀🚀🚀