Remove limitations on full text functions in ES|QL

**What the feature is**

Full text functions cannot be currently used in ES|QL after pipeline breakers or on runtime columns. We will lift both of these restrictions.

**Value proposition**

This change will reduce user friction and enable advanced search capabilities not available in query DSL via search on runtime columns. By allowing for full text functions after pipeline breakers, we enable actions like rescoring, and by allowing for search on runtime columns, users can go beyond keyword matching on these columns, but instead search on full text.

Example of a full text function after a pipeline breaker (`LIMIT`):

```
FROM books
| WHERE title:?query
| SORT title DESC
| LIMIT 100
| WHERE description:?query
```

Example of a full text function on a runtime column (syntax not finalized):

```
FROM books METDATA _score
| STATS languages = VALUES(language),
titles = VALUES(title),
rating = MAX(rating) BY code
| SORT rating DESC
| LIMIT 100
| WHERE match(titles, "Harry Potter")
OR match(titles, "Harry Potter", { "index_analyzer": "my_analyzer"})
```

**Expected outcome**

Users can use full text functions after pipeline breakers or on runtime columns in ES|QL.