Change API utilized by ICEC PeopleFinder widget

The PeopleFinder widget is using a different API then the Advanced Search. PeopleFinder widget fails to return results if the term includes a "-" character or string followed by any character i.e. "intra-kummi". However, the API used for Advanced Search does not have this problem as it returns results for the same term.

Here is API used by PeopleFinder widget:

e.g.

https://<connections_server>/profiles/atom/search.do?activeUsersOnly=true&format=full&ps=100&search=FIELD_DISPLAY_NAME:intra\-kummi*%20OR%20FIELD_NAMES:intra\-kummi*%20OR%20FIELD_TELEPHONE_NUMBER:intra\-kummi*%20OR%20FIELD_MOBILE:intra\-kummi*%20OR%20FIELD_IP_TELEPHONE_NUMBER:intra\-kummi*%20OR%20FIELD_JOB_RESPONSIBILITIES:intra\-kummi*%20OR%20FIELD_DEPARTMENT_TITLE:intra\-kummi*%20OR%20FIELD_TAG:intra\-kummi*%20OR%20FIELD_PHYSICAL_DELIVERY_OFFICE:intra\-kummi*&_=1559202901760

and here is API used by Advanced Search (entering term in Tag field and w/ Profiles checkbox selected):

https://<connections_server>/search/atomfba/mysearch?scope=allconnections&scope=profiles&query=intra-kummi&personalization=%7B%22type%22%3A%22personalContentBoost%22%2C%22value%22%3A%22on%22%7D&page=1&pageSize=10&format=light

As we can see, the PeopleFinder widget is using the Profiles Search API and the Advanced Search is using the Search API.

The Profiles Search API respects the dash character as a NOT operator which excludes results that contain anything after the dash character.

Customer requesting to fix the code within the PeopleFinder.js to utilize an API which will support typeahead search and not recognize the dash character as a NOT operator.

Not sure if the Search API would be best candidate as it is not recommended to be used to support a typeahead experience.

The Social People Finder seems like a good candidate as it is a form of typeahead search, but it returns JSON instead of Profiles Feed (xml enry).