frontend: Add create resource UI

[skoeva]

These changes introduce a new UI feature that allows users to create resources from the associated list view. Clicking the 'Create' button opens up the EditorDialog used in the generic 'Create / Apply' button, now accepting generic YAML/JSON text rather than explicitly expecting an item that looks like a Kubernetes resource. The dialog box also includes a generic template for each resource. The apply logic for this new feature (as well as the original 'Create / Apply' button) has been consolidated in EditorDialog, with a flag allowing external components to utilize their own dispatch functionality.

Fixes: #1820

Testing

Create resource button

• Open a cluster in Headlamp (cd app & npm start) and navigate to a resource (e.g. Config Maps)
• Click the + sign in the header and ensure the appropriate template appears in the editor
• Apply changes and ensure the created resource appears in the list view

EditorDialog changes

• Open Headlamp (cd app & npm start) and click the 'Create / Apply' button
• Pass in a list of resources to the editor (e.g. a list of Config Maps)
• Apply changes and ensure that all the resources in the list appear in the list view

Screenshots

[ashu8912]

These are some nice set of changes thanks @skoeva I was wandering what all resources we are covering to have the create resource button on?? And what is the reasoning behind adding it to some and not to others if that's the case?

[skoeva]

These are some nice set of changes thanks @skoeva I was wandering what all resources we are covering to have the create resource button on?? And what is the reasoning behind adding it to some and not to others if that's the case?

@ashu8912 Currently covering config maps, secrets, leases, and runtime classes as those I already found with base templates in their associated directories, though if needed, we can add templates for more resources and cover those as well

[illume]

Nice work!

I left a few notes for your consideration.

As well as a CreateResourceButton.stories.tsx, maybe a few small pieces could be unit tested, and perhaps an e2e test would be useful for the overall feature?

(ps. it also needs rebasing against main now)
(pps. good work on adding the kube-ish function, we should validate the data matches what we're expecting a bit more... especially since we need to fix a bunch of types still)

[illume]

These are some nice set of changes thanks @skoeva I was wandering what all resources we are covering to have the create resource button on?? And what is the reasoning behind adding it to some and not to others if that's the case?

@ashu8912 Currently covering config maps, secrets, leases, and runtime classes as those I already found with base templates in their associated directories, though if needed, we can add templates for more resources and cover those as well

Probably you know this already... but the k8s website gives example yaml for each resource in their docs. But adding defaults for all the resources could be left for a future PR I reckon... it shouldn't block merging IMHO.

[joaquimrocha]

I have spotted something simple that needs to be improved in the code, but I have tested the feature again (creating a new item) and there's an inconsistency against the normal Create button:
When there's a failure to create a resource, the creation dialog should be brought back up again, and it's not in the case of this creation UI.

Steps to reproduce:

1. Start creating a Node from the new + button
2. Make sure you add an invalid name like my-super-node-
3. Verify that it silently fails: no notification, and the dialog is not brought up. When then opening the dialog again, the error is there