chore(ui): check Op code for literal credentials

[jamie-rasmussen]

Description

https://wandb.atlassian.net/browse/WB-21683

After:

Testing

How was this PR tested?

[circle-job-mirror]

Preview this PR with FeatureBee: https://beta.wandb.ai/?betaVersion=e5898750f93aae764db3710b5675faf4bec3164e

[gtarpenning]

I wonder if the message doesn't convey enough information for the user to act on it? Like if I see '<Redacted: string contains Authorization pattern>' I'm not sure I would instantly know that this is generated from {"authorization": ...}. Although i guess we should always be sanitizing and this is just for existing key stuff?

[jamie-rasmussen]

I wonder if the message doesn't convey enough information for the user to act on it? Like if I see '<Redacted: string contains Authorization pattern>' I'm not sure I would instantly know that this is generated from {"authorization": ...}. Although i guess we should always be sanitizing and this is just for existing key stuff?

Yes, this is a last line of defense in case of sanitization failures. I agree that it isn't a very actionable message but not clear what we would want user to do about it either.