)

PR for issue #93.

Adding bzlmod instructions for inclusion of this project as an external
dependency.

---------

Co-authored-by: jchadwick-buf <116005195+jchadwick-buf@users.noreply.github.com>

This updates protovalidate-cc to use the new v0.12.0 release of
protovalidate.

This updates the repo to the v1.0.0-rc.1 release candidate for
Protovalidate.

Hurray, cel-cpp is now in the BCR as of a month ago. Let's get ourselves
one step closer to the BCR by pulling from it. We don't need the Windows
patch in Bazel since cel-cpp still doesn't work in Bazel on Windows
anyways (maybe next release...)

Unfortunately we will probably need a couple of tries to get this right,
but hopefully this is very close to what we want.

Closes #98.

This may not be all. I apologize for the noise.
- I mistyped the version number. For semver it's better to do rc.2 than
rc2. (Looking at the BNF, I'm not sure that the latter is expressly
disallowed, though.)
- Also, I need to add attestation privileges to the workflow dispatch
job.

Like I said... sorry for the noise. :) (Will try to balance around
different people to bug for these small PRs.)

I almost hit publish before realizing that I failed to specify the BCR
fork to publish using in thepublish workflow inputs.

Also, fix a race condition by ensuring that the release job does not run
prior to the create-release-tag job.

Publish to BCR needs id-token + attestations.

Hopefully the last one?...

Closer...

Upstream merged my PR.

(This will also prevent future attestations from failing.)

Not urgent but looks like we'll need this to actually make the BCR
release work all the way.

It seems to not like an explicit commit ref... will it accept a branch
ref instead? I tried looking at the SLSA source code to find out, but
it's going to be easier to just try. If not I need to bug them to make a
new release because a change we need is not tagged yet.