(feat) O3-4315: Add support for workspace-launcher rendering type

[rdwaynedehoedt]

Requirements

• This PR has a title that briefly describes the work done including the ticket number. If there is a ticket, make sure your PR title includes a conventional commit label. See existing PR titles for inspiration.
• My work conforms to the OpenMRS 3.0 Styleguide and design documentation.
• My work includes tests or is validated by existing tests.

Summary

This PR implements the workspace-launcher rendering type for form questions as specified in O3-4315. The workspace-launcher allows form creators to add buttons that launch different workspaces or sub-forms within the OpenMRS application, enhancing clinical workflow integration.

The implementation includes:

• A new workspace-launcher.component.tsx component with input fields for buttonLabel and workspaceName
• Updates to the QuestionOptions interface in types.ts to include these new properties
• Registration of the component in the inputs index and component map
• Integration with the existing form builder architecture

This feature is part of the O3 Form Builder v3 epic (O3-1144).

Related Issue

https://openmrs.atlassian.net/browse/O3-4315

Other

The workspace-launcher rendering type follows the specified JSON structure:

"questionOptions": {
  "rendering": "workspace-launcher",
  "buttonLabel": " ",
  "workspaceName": ""
}

[rdwaynedehoedt]

Hi @NethmiRodrigo , could you review this PR Thanks!

[Bharath-K-Shetty]

@rdwaynedehoedt Please add a video demonstrating that everything still behaves as expected & add unit test covering this change.

[NethmiRodrigo]

Thanks @rdwaynedehoedt! Good work! Please look at the comments and include a screenshot of the UI and how it works in the description. Its also preferred to add unit tests for new functionality, similar to how the other inputs do.

[NethmiRodrigo]

Almost there @rdwaynedehoedt! Some minor changes. Excellent test cases!

[NethmiRodrigo]

Thanks @rdwaynedehoedt! One last thing :)

[NethmiRodrigo]

This is good to have, but we can make it a bit better by checking if it got called with the right object. Here's a place where you can use for guidance -

openmrs-esm-form-builder/src/components/interactive-builder/modals/question/question-form/question-types/inputs/obs/obs-type-question.test.tsx

Lines 115 to 129 in d80c228

	// Gets all calls made to our mock function, the arguments from the first call and the first argument of the first call
	const updateFn = mockSetFormField.mock.calls[0][0];
	// Execute the update function with the previous state
	const resultState = updateFn(formField);
	// Check that the result has the expected values
	expect(resultState).toEqual({
	...formField,
	datePickerFormat: 'calendar',
	questionOptions: {
	...formField.questionOptions,
	concept: '456',
	},
	});

[NethmiRodrigo]

Pinging @rdwaynedehoedt, are you stuck on any part of updating the tests, if so do let me know and I'll try to help out