feat: expose Monaco and Dynamic Page as Web Components

[OliwiaGowor]

Description

Changes proposed in this pull request:

• added a generic function for creating Web Components
• added Monaco Editor Web Component
• added Dynamic Page Web Component
• added documentation for Web Components

Related issue(s)
Closes #3520

Definition of done

• The PR's title starts with one of the following prefixes:
  • feat: A new feature
  • fix: A bug fix
  • docs: Documentation only changes
  • refactor: A code change that neither fixes a bug nor adds a feature
  • test: Adding tests
  • chore: Maintainance changes to the build process or auxiliary tools, libraries, workflows, etc.
• Related issues are linked. To link internal trackers, use the issue IDs like backlog#4567
• Explain clearly why you created the PR and what changes it introduces
• All necessary steps are delivered, for example, tests, documentation, merging

[mrCherry97]

/hold @pbochynski review

[pbochynski]

The script for custom extension is loaded only if web component defined in general.customElement is not defined yet. The idea was that all custom extensions introduce own custom elements and this way we can lazily load the script (only once: see the code). The example provided in this PR is not complete (missing general section) and does not define a web component for custom extension. If developers will start to use it as it is it will work, but with each render of the custom extension script element will be added to the DOM document. I am not sure if it is intended.

[pbochynski]

It would be nice if the example uses dynamic page and looks exactly as other views. Currenlty it is displayed like this:

It would be nice if it looks like this:

[pbochynski]

Suggested change

	To set up and deploy this exmaple, follow [this]('examples/../../custom-extension/README.md) documentation.
	To apply this example in your cluster execute:
	```bash
	kubectl kustomize . | kubectl apply -n kyma-system -f -

For more information follow this documentation.

[grego952]

This command is provided as an alternative in the Custom Extension README. Does it mean that this command covers all previous steps (1. Enable custom extensions in your cluster, 2. Adjust the static HTML content, etc)? Or should a user execute this one first and then follow 1., 2., 3. 4. from the example?

[grego952]

This command is provided as an alternative in the Custom Extension README. Does it mean that this command covers all previous steps (1. Enable custom extensions in your cluster, 2. Adjust the static HTML content, etc)? Or should a user execute this one first and then follow 1., 2., 3. 4. from the example?