deps: update cel-cpp

[kyessenov]

Commit Message: Updates cel-cpp to latest in OSS. There's another export coming so this PR will be followed up. However, the new export needs the latest protoc, absl, and re2 - which may cause other problems. There is a macro pollution problem with proxy-wasm/proxy-wasm-cpp-sdk#154 addressed by a local patch. I will upstream cel-cpp patch separately.

Risk Level: low
Testing: unit
Docs Changes: none

[repokitteh-read-only]

CC @envoyproxy/dependency-shepherds: Your approval is needed for changes made to (bazel/.*repos.*\.bzl)|(bazel/dependency_imports\.bzl)|(api/bazel/.*\.bzl)|(.*/requirements\.txt)|(.*\.patch).
envoyproxy/dependency-shepherds assignee is @htuch

🐱

Caused by: #27414 was opened by kyessenov.

see: more, trace.

[kyessenov]

MSVC does not support weak linkage with ABSL_ATTRIBUTE_WEAK.
I'm not sure how to resolve this apart from disabling CEL on windows. CC @jcking

[kyessenov]

It turns out the weak linkage is not necessary for this version of CEL since the new code is not active.

[htuch]

+1 on upstreaming the CEL patches, they look painful to maintain.

[phlax]

@kyessenov it seems this is throwing a lot of warnings in our build - a lot seem to be essentially the same warning

Im guessing we can ~safely ignore the warnings - if so im wondering if we can suppress them in the patch or similar

[tyxia]

Thank you very much for the help with updating CEL!

[kyessenov]

@phlax Yeah I'll fix those warnings upstream. I wanted to unblock @tyxia while we figure out how to build the latest (still not exported) CEL.

[kyessenov]

A new update to cel-cpp is in progress google/cel-cpp#167, but it requires very recent protoc/absl - which will not happen quickly.

[yanavlasov]

Will apply the changes in the patch to the cel-cpp SoT repo. However we still need to sort out some issues before we can use cel-cpp HEAD. At this point this will allow CEL matcher work to proceed and patch will go away once we can finally depend on the most recent cel-cpp.