PZP friendly name shown instead of the full URL

Jira Issue: WP-263
PZP friendlyname is enforced for communication with WRT

Re-introduced update from PZH to PZP on event, it includes friendlyname and connectedPzp/connectedPzh friendlyName. This is for display purpose.
FindService and App2App peerId, has id replaced when communicating with PZPWSS and Browser.
Solves issue with the contacts where it reads wrong session id information.

Jira Issue: WP-263
Fixed address from friendlyName to originalId

Jira Issue: WP-263
Update message and few issue fix up

Reintroduced update message from PZH to PZP about connected devices information including friendlyName.
PZP WebSocket server replaces every message message header with friendlyName.

Jira Issue: WP-263
PZP websocket and client side pzhid handling

Corrected Pzhid handling on the client side

Jira Issue: WP-263
PZP sending friendlyname and key to the PZH at time of reconnect

Jira Issue: WP-263
Device friendly name

Message sent to connected PZP and PZH

Jira Issue: WP-263
Friendly name mapping that works across PZs

Jira Issue: WP-263
Friendly name updates in PZH and Service discovery

Jira Issue: WP-263
Few path checks to avoid PZP crash

Jira Issue: WP-263
PZP set friendly name interface fixes

Jira Issue: WP-263
Friendly name setting support removed

Based on code review comment

Jira Issue: WP-263
Rebase not properly done

Jira Issue: WP-263
Merge pull request #469 from habibvirji/WP-263-device-friendly-name-mapping

Wp 263 device friendly name mapping