[CL-1097] Search by content from content builder

[alexander-cit]

No description provided.

[cl-dev-bot]

	Warnings
⚠️	The branch name contains no Jira issue key (case-sensitive)
⚠️	The changelog hasn't been modified

	Messages
📖	Jira issue: CL-1097

Generated by 🚫 dangerJS against e1251cd

[alexander-cit]

@sebastienhoorens @IvaKop do you agree that props.text (second level of nesting, hence *.* here) is the only valuable text we should search against?

In my DB, it looks like that

{
  "en": {
    "ROOT": {
      "type": "div",
      "nodes": ["nfXxt3641Y"],
      "props": { "id": "e2e-content-builder-frame" },
      "custom": {},
      "hidden": false,
      "isCanvas": true,
      "displayName": "div",
      "linkedNodes": {}
    },
    "1pzsxkGIsQ": {
    ...
    },
    "eLuxCVwxvY": {
      "type": { "resolvedName": "Text" },
      "nodes": [],
      "props": { "text": "\u003cp\u003eqwe\u003c/p\u003e" },
      "custom": {},
      "hidden": false,
      "parent": "4-5gDdwOpm",
      "isCanvas": false,
      "displayName": "Text",
      "linkedNodes": {}
    }
   }
}

[IvaKop]

@alexander-cit This is the case for the text component but I think there might be other content builder components where there might be relevant information for the search - like the title prop in the accordion, for example. Could you ask the methods squad for a comprehensive list?

[nTraum]

Just one small typo fix, then this is good to go. :)

[nTraum]

LGTM!

[nTraum]

@alexander-cit Can we merge this beauty? 🍏

[alexander-cit]

@nTraum I want to write one more test for it (search two projects against both content and body). I hope I'll do it today and then I'll merge.