scheduled_transitions_tokens expects string but can receive int

Problem/Motivation

Similar to 🐛 Incorrect type hinting in the smart_trim_tokens function Active in smart trim, we get a fatal error when using a token filter and the body content contains something like [1:1]. There's more info in the core issue at 🐛 Numeric content inside square brackets within a node body recognised as a token with a type of int Active , but for now we probably need to allow non-string values.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes