Update cel expressions for standard constraints with bool type

[oliversun9]

This fixes the problem where

message Foo {
  string bar = 1 [(buf.validate.field).string.tuuid = false];
}

still validates for tuuid by updating cel expressions to pass if the option is set to false.

[github-actions]

The latest Buf updates on your PR. Results from workflow Buf CI / buf (pull_request).

Build	Format	Lint	Breaking	Updated (UTC)
✅ passed	✅ passed	✅ passed	✅ passed	Sep 11, 2024, 9:38 PM

[rodaine]

Can we add conformance tests that check these as well as run it against protovalidate-go to verify? Thanks @oliversun9!

[jchadwick-buf]

I think the changes mostly LGTM though I echo the sentiment re: adding conformance test cases, definitely a good idea.

[oliversun9]

Can we add conformance tests that check these as well as run it against protovalidate-go to verify? Thanks @oliversun9!

I added tests and build pvgo's conformance test binary with locally generated protovalidate code, and they pass 😄

go build -o .tmp/bin/protovalidate-conformance ./tools/protovalidate-conformance
PASS (failed: 0, skipped: 0, passed: 1800, total: 1800)

[jchadwick-buf]

LGTM, passes just fine. This does however make me realize that I need to improve the reparse logic on my branch. Even with my new improvements, I still couldn't get conformance passing without updating the gencode. (This is wrong, conformance should pass in the future even with completely mismatched gencode.)