The deprecation annotation about colon in unquoted YAML values has false positives

[stof]

The only case triggering an issue is having a colon followed by a space. A colon followed by another char does not cause any issue, but your plugin still reports a warning on such values.

[stof]

Actually, it looks like the remaining false positive is only when the colon is the last char of the string

[Haehnchen]

@stof any example?

[stof]

Here is a case I got, which is really weird, as there is no colon in the ^/join/[\w\-\=]++~[a-z0-9\-]++$ value being reported.

security:
    access_control:
        - { path: ^/join/[\w\-\=]++~[a-z0-9\-]++$ }

[stof]

I think this happens when the value contains such [] chars

[stof]

This also happens when the : is the last character of the value