Add an additionally needed “requires Text Analytics Toolbox” for one of the examples which uses `tokenizedDocument`.

Refactor for readability

Refactoring of Ollama.md

Most  models accept both `max_tokens` and `max_completion_tokens`; the newer reasoning models only want to see `max_completion_tokens`, while GPT-3.5 deployments error when given `max_completion_tokens`. Since we do not know which model is behind some deployment name, we just try with the newer name and come back with the old name if we get the corresponding error message.

The test point also works with o1-mini, gpt-4o is just cheaper.

* Make test point less brittle

`tazureChat/generateWithStructuredOutput` has somewhat frequent spurious failures of this type:

```
  ================================================================================
  Verification failed in tazureChat/generateWithStructuredOutput.
      ---------------------
      Framework Diagnostic:
      ---------------------
      OrConstraint failed.
      --> + [First Condition]:
           |   OrConstraint failed.
           |   --> + [First Condition]:
           |        |   IsEqualTo failed.
           |        |   --> StringComparator failed.
           |        |       --> The strings are not equal.
           |        |
           |        |       Actual Value:
           |        |           "western honey bee"
           |        |       Expected Value:
           |        |           "honeybee"
           |   --> OR
           |       + [Second Condition]:
           |        |   IsEqualTo failed.
           |        |   --> StringComparator failed.
           |        |       --> The strings are not equal.
           |        |
           |        |       Actual Value:
           |        |           "western honey bee"
           |        |       Expected Value:
           |        |           "honey bee"
           |       -+---------------------
      --> OR
          + [Second Condition]:
           |   IsEqualTo failed.
           |   --> StringComparator failed.
           |       --> The strings are not equal.
           |
           |       Actual Value:
           |           "western honey bee"
           |       Expected Value:
           |           "bee"
          -+---------------------
```

Rather than trying to add more and more valid alternatives, it is probably better to relax the requirements a bit.

* Make test less noisy

`texampleTests/testAnalyzeTextDataUsingParallelFunctionCallwithOllama` was lacking the `evalc` against noise cluttering the output.