Those in charge of the C++ style guide choose not to allow them without strong justification. In practice, you just convince your reviewer and move on. Most reviewers are reasonable, but edge cases a where it is needed are rare.
I don’t especially like it, but in terms of annoying style issues, it is very far down the list, especially when the tooling handles it all for you via auto formatting and whatnot.
You just have to convince your reviewer it makes sense in that particular case. The more obvious it is, the easier it will be.
Can you give one?
At the very least you can inspect your test data easily without having to extract it from base64-encoded strings.
Current approach may be working for your team, but I can totally see why a company which has a dedicated team working on build and testing infra, prefers a slightly more complex approach. It requires one-off investment in tooling which can be payed off very soon given enough people using it.
Of course you can embed binary files as base64, but have you thought if you should
Are the tools at Google and elsewhere unable to diff code if a line exceeds some arbitrary width?