Session-ID and Search-Session-ID for search table

[mulundapm]

• Add session id and search session id to search table
• Add search session id to search clicked table

I propose to add 2 headers to the search requests:

X-Session-ID, X-Search-Session-ID

X-Session-ID: This is the session id that the Frontend is sending to rudderstack. This enables easier correlation of events from backend with events in frontend (for example, tracking of "clicks" on search results)

X-Search-Session-ID: New ID that gets reset every time user opens the search page, so one search session may consist of many partial search queries like "He", "Her", "Hero". This is logically speaking one search and if user gets a desired result on any of this we can probably consider it a success even if they type "Herox", and then correct it back to "Hero", because "Herox" did not deliver any (good) results.