This PR adds a new section in the screen builder that dynamically populates with templates when the 'Templates' button is selected. It fetches both user-specific and shared templates via API calls and displays the results in the right panel of the screen builder.

Changes

• Implemented API calls to retrieve both "My Templates" and "Shared Templates" data from the backend.
• Added a new section in the right panel of the screen builder to display the retrieved templates when the 'Templates' button is clicked.

How to Test

1. Navigate to the screen builder interface.
2. In the screen builder navigation menu, click the 'Templates' button to trigger the template loading process.
3. Ensure that API calls are made to fetch "My Templates" and "Shared Templates" correctly.
4. Once the templates are retrieved, confirm they are displayed in the right panel under appropriate categories (e.g., "My Templates" and "Shared Templates").

Related Tickets & Packages

FOUR-18286
Screen Builder PR

ci:next
ci:screen-builder:subtask/FOUR-18286

Code Review Checklist

• I have pulled this code locally and tested it on my instance, along with any associated packages.
• This code adheres to ProcessMaker Coding Guidelines.
• This code includes a unit test or an E2E test that tests its functionality, or is covered by an existing test.
• This solution fixes the bug reported in the original ticket.
• This solution does not alter the expected output of a component in a way that would break existing Processes.
• This solution does not implement any breaking changes that would invalidate documentation or cause existing Processes to fail.
• This solution has been tested with enterprise packages that rely on its functionality and does not introduce bugs in those packages.
• This code does not duplicate functionality that already exists in the framework or in ProcessMaker.
• This ticket conforms to the PRD associated with this part of ProcessMaker.