fix(proto): limit refresh-token scope items to the RFC 6749 charset
A Doorkeeper refresh-token event is now refused when a scope item falls outside the RFC 6749 scope-token charset. The repository stores the scope list as one space-joined string and splits it on read (!1010 (merged)), so an item like read write would come back as two scopes. The charset also refuses NUL, which Postgres text cannot store. Rails splits on spaces before it sends, so no real event changes; the rule closes the gap for a hand-built client.
The rule is a buf.validate pattern on the scopes items of the single-record Upsert request, which the bulk upsert in !991 (merged) reuses per record. validateToken checks the same charset next to the encoding, so callers that skip protovalidate are covered too. Validation cases cover each excluded character class and the range edges.