Improve Wait for Response documentation: clarify criteria, add missing fields and examples

[soniasachdeva]

Doc: docs/4. Product Features/03. Flows/2. Flow Actions/04. Wait for the contact to respond.md

Problem:
In the "Text-based responses" section, the criteria has all of the words, has a phrase, and has only the phrase only have a one-line description each, with no worked example — unlike has any of the words, which includes a clear example. The current wording is also ambiguous (e.g., "has all of the words" reads like an exact match, which is actually the behavior of "has only the phrase").

Current text:

### 2. has all of the words
To accept the input if the input matches exactly what is defined in the response criteria.

### 3. has a phrase
To accept the input if the input is present in the response criteria.

### 4. has only the phrase
Accepts only if the response matches exactly what is defined in the response criteria.

Proposed change:
Add a short example (similar in style to the "has any of the words" entry) under each of the following, and tighten the wording so the distinction between them is clear:

• has all of the words — Accepts the input if it contains all of the words listed in the criteria, in any order. Example: Criteria = red, apple → "I want a red apple" ✅, "I want a red banana" ❌ (missing "apple").
• has a phrase — Accepts the input if the exact phrase (sequence of words, in that order) appears anywhere in the response. Example: Criteria = good morning → "good morning, how are you?" ✅, "morning, good sir" ❌ (words out of order).
• has only the phrase — Accepts the input only if it matches the criteria exactly, with nothing else. Example: Criteria = good morning → "good morning" ✅, "good morning!" or "good morning to you" ❌.

Acceptance criteria:

• Each of the three criteria has at least one example, formatted consistently with "has any of the words."
• Wording reviewed for accuracy against actual flow-engine behavior before publishing.
• Optional: add a screenshot for each, matching the pattern used elsewhere in the doc.

---

Expanded scope (implemented together in PR #666):

While addressing the above, a full review of the same page turned up related problems that were fixed in the same pass, since it's the same doc and the same reader confusion:

• Fixed a typo in the "has a number between" example screenshot ("Kida" → "Kids"), and added a note that overlapping ranges (e.g. 20-60 and 60-100) resolve to the first matching row — verified on staging.
• Aligned every text example on the page with what its accompanying screenshot actually shows (numeric ranges/cases, phone/email/media categorization and result names, regex example) instead of generic placeholders.
• Fixed duplicated/invalid "has an email" examples.
• Documented the @results.<name>.url syntax for has audio, has video, has image, and has file. Verified on staging that only the URL resolves for these four (not .caption — that only works for has media).
• Renamed "has a phrase" to "has the phrase" to match the live dropdown label.
• Added two criteria that exist in the live dropdown but were undocumented: "has multiple values" and "starts with" (verified against Glific.Flows.Case.do_execute/2).
• Added an "Understanding the fields in this node" section explaining every blank field in the Wait for Response dialog.
• Added a "The no-response branch in your flow" section with a canvas screenshot, clarifying the difference between the automatic "Other" branch and "No Response."
• General grammar and plain-language cleanup across the page.

See PR #666 for the full diff.