Proper bazel support

[aaomidi]

The expected way expr is supposed to be imported in Go is: "cel.dev/expr" however, that links to https://github.com/google/cel-spec/blob/master/BUILD.bazel which is empty. This means any downstream users of this library that are using bazel get a broken experience.

I believe a go_library with name of "expr" needs to be defined in that build file.

[TristonianJones]

Hi @aaomidi I've been looking into some of the issues here and should have some fixes next week. Thanks for your patience!

[aaomidi]

Just in case anyone is interested in how I ended up working around this problem:

go_deps.gazelle_override(
    # Force Gazelle to wipe out the existing build files before regenerate them.
    build_file_generation = "clean",
    directives = [
        "gazelle:resolve proto go google/rpc/status.proto @org_golang_google_genproto_googleapis_rpc//status",
        "gazelle:resolve proto proto google/rpc/status.proto @googleapis//google/rpc:status_proto",
    ],
    path = "cel.dev/expr",
)

There's probably some negative side effects of this, but I haven't noticed any yet.