Ignore mso comments

@milanbombschliip thank you for the bug report and patch. I have some thoughts.

First, does the reported issue occur when the Token module is enabled but Token OR is not enabled? In other words, is this issue specific to Token OR?

Second, I would prefer a general solution versus adding code for a specific circumstance, like Microsoft Office email tags. Approaching this issue by making an exception for MSO is not scalable. We should get to the root cause.

Finally, we will need tests in order for any patch to be considered.

Thanks for working on this and identifying the issue.

I reviewed the current approach and the fix works for the reported case. Building on that, I think we can make it more robust by avoiding hardcoded checks for only `[if mso | IE]` and `[endif]`, since there are several other common MSO conditional variants used in email templates, for example:

* `[if mso]`
* `[if gte mso 9]`
* `[if lt mso 16]`
* `[if !mso]`
* `[if mso 12]`

A regex-based approach would help cover all of these cases more reliably.

In `src/TokenOrTokensPreAlter.php`, we could consider replacing the hardcoded check with:

```php id="cw4ywg"
foreach (reset($matches) as $match) {
// Skip MSO/IE conditional comment syntax (e.g. [if mso], [if gte mso 9], [endif]).
if (preg_match('/^\[(?:if\b|endif\b)/i', $match)) {
continue;
}

if (strpos($match, '|') !== FALSE) {
```

This would cover all MSO conditional variants without needing to hardcode specific strings.

@milanbombschliip if the work from @mukeshaddweb is added, we will need extensive test coverage for it.

@milanbombschliip I appreciate your work on this. Your issue fork is valuable because it provides a temporarily fix with the patch that can be applied with composer. However, I still prefer a more generalized approach like @mukeshaddweb suggests. This ticket remains the best place to do that.

Committed to 2.x, thanks everyone!

@milanbombschliip thank you for the report, the MR, and especially the test. It's kept as-is in the final commit. @mukeshaddweb thanks for pushing toward a general solution.

Instead of matching specific MSO strings, Token OR now only treats bracketed text containing a | as an OR token when at least one part is a real token (type:name) or a quoted string. Anything else is left untouched, even with 'clear' => TRUE. That covers every MSO conditional variant ([if mso | IE], [if !mso | IE], [if lt mso 16 | IE], …) as well as any other non-token text that happens to contain a pipe.

Existing OR tokens behave exactly as before, including ones with a typo in one of the alternatives, e.g. [node:title|not a token] still resolves to the title.

This will be in the next 2.x release.