AB#68534 - People Picker for forms

[Joselgc1]

Description

The People Picker feature is now fully completed. Building on the initial version, which already had the basic field working in SurveyJS with lazy-loaded search and correct value storage, we now support two field types: People (Single) and People (Multiple), both available in the SurveyJS toolbox. Search has been switched from the old Apollo client setup to the Common Services REST endpoint, still using debounce, and showing results in the "FirstName LastName (email)" format. The multi-select field now displays chosen users as removable chips for a much clearer UX.

We improved how values are stored. Instead of saving just the userid, each selection now stores the full user object (firstname, lastname, email, userid). This solves the remaining Grid-related tasks: grids can display names immediately without extra lookups, and sorting and filtering work smoothly because all relevant metadata is already available. Grid rendering is now fully functional for both single- and multi-select fields.

Pagination is no longer needed since the REST endpoint only supports whole-word matching.

Type of change

Please delete options that are not relevant.

• New feature (non-breaking change which adds functionality)
• Improvement (refactor or addition to existing functionality)

Checklist:

( * == Mandatory )

• * I have set myself as assignee of the pull request
• * My code follows the style guidelines of this project
• * Linting does not generate new warnings
• * I have performed a self-review of my own code
• * I have put the ticket for review, adding the oort-frontend team to the list of reviewers
• * I have commented my code, particularly in hard-to-understand areas
• * I have put JSDoc comment in all required places
• * My changes generate no new warnings
• * I have included screenshots describing my changes if relevant
• * I have selected labels in the Pull Request, according to the changes with code brings
• I have made corresponding changes to the documentation ( if required )
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules