Add `Deploy to OpenShift/Podman` action to folder in workspace

[mohitsuman]

When using VSCode to create a new component in a project, the "Create Component" functionality currently requires selecting a workspace for the component.

This issue proposes the addition of an "Deploy to OpenShift/Podman" option to streamline the process and eliminate the need to navigate through files and directories repeatedly.

Acceptance Criteria:

• The "Create Component" functionality should be enhanced with an additional option named "Deploy to OpenShift/Podman"
• When the user selects the "Deploy to OpenShift/Podman" option, the component creation process should automatically use the currently opened workspace directory as the location for the new component.
• when the current workspace is not a valid project directory, an informative error message should be displayed, indicating that a valid workspace must be open for this option to work.
• The "Deploy to OpenShift/Podman" option should be displayed prominently in the Folder right click context menu, ensuring its visibility and accessibility to users.
• If the user chooses to create a component using the traditional method of selecting a workspace manually, the existing functionality should remain unaffected.
• Proper error handling should be implemented to gracefully handle any unexpected scenarios or errors that may arise during the process.
• The new feature should be well-documented in the Welcome and Walkthrough documentation, including clear instructions on how to use the "Deploy to OpenShift/Podman" option.

Additional Notes:
This enhancement would greatly improve the user experience for developers working with VSCode, making the process of creating components within an existing workspace more efficient and user-friendly. The implementation should be carefully reviewed and tested to ensure its seamless integration with the existing functionality and to avoid introducing any regressions.