Digest function now auto-detected from request

[allada]

The digest function the client requested is now properly implemented
in the OriginContext. This allows us to inspect what digest-function
the client requested from anywhere in the code.

---

This change is 

[allada]

+@adam-singer

This is dependent on the previous PR landing first.

Reviewable status: 0 of 1 LGTMs obtained, and pending CI: Analyze (javascript-typescript), Analyze (python), Bazel Dev / ubuntu-22.04, Cargo Dev / macos-13, Cargo Dev / ubuntu-22.04, Local / ubuntu-22.04, Publish image, Publish nativelink-worker-lre-cc, Remote / large-ubuntu-22.04, asan / ubuntu-22.04, docker-compose-compiles-nativelink (20.04), docker-compose-compiles-nativelink (22.04), integration-tests (20.04), integration-tests (22.04), macos-13, pre-commit-checks, ubuntu-20.04 / stable, ubuntu-22.04, ubuntu-22.04 / stable, vale, windows-2022 / stable (waiting on @adam-singer)

[adam-singer]

Reviewed 11 of 11 files at r1, 12 of 12 files at r2, all commit messages.
Reviewable status: complete! 1 of 1 LGTMs obtained

[allada]

I think this is the final form.

Local testing shows it working, but still need more larger testing.

I can break this into 1 maybe 2 PRs if you prefer, but most of this is related.

Reviewable status: 1 of 1 LGTMs obtained, and pending CI: Vercel, pre-commit-checks

[adam-singer]

Reviewed 34 of 34 files at r3, all commit messages.
Reviewable status: 1 of 1 LGTMs obtained, and pending CI: Remote / large-ubuntu-22.04, and 1 discussions need to be resolved

---

nativelink-scheduler/tests/cache_lookup_scheduler_test.rs line 119 at r3 (raw file):

        let action_name = ActionInfoHashKey {
            instance_name: "instance".to_string(),
            digest_function: DigestHasherFunc::Sha256.proto_digest_func().try_into()?,

Why does this need to do a try_into when the other passed ones in action_messages_test.rs didnt?

[allada]

Reviewable status: 1 of 1 LGTMs obtained, and pending CI: Analyze (javascript-typescript), Bazel Dev / ubuntu-22.04, Vercel, pre-commit-checks, ubuntu-20.04 / stable, ubuntu-22.04, vale, and 1 discussions need to be resolved

---

nativelink-scheduler/tests/cache_lookup_scheduler_test.rs line 119 at r3 (raw file):

Previously, adam-singer (Adam Singer) wrote…

Why does this need to do a try_into when the other passed ones in action_messages_test.rs didnt?

Copy pasta failure. Fixed.

[adam-singer]

Reviewed 1 of 1 files at r4, all commit messages.
Reviewable status: 1 of 1 LGTMs obtained, and pending CI: Remote / large-ubuntu-22.04, and 1 discussions need to be resolved

---

nativelink-scheduler/tests/property_modifier_scheduler_test.rs line 251 at r5 (raw file):

        let action_name = ActionInfoHashKey {
            instance_name: "instance".to_string(),
            digest_function: DigestHasherFunc::Sha256.proto_digest_func().try_into()?,

nit: DigestHasherFunc::Sha256.proto_digest_func().try_into()? -> DigestHasherFunc::Sha256

[adam-singer]

Reviewed 10 of 10 files at r6, all commit messages.
Reviewable status: 1 of 1 LGTMs obtained, and pending CI: Remote / large-ubuntu-22.04

[allada]

Reviewable status: 1 of 1 LGTMs obtained, and pending CI: Analyze (javascript-typescript), Analyze (python), Bazel Dev / ubuntu-22.04, Cargo Dev / macos-13, Cargo Dev / ubuntu-22.04, Installation / macos-13, Installation / macos-14, Installation / ubuntu-22.04, Local / ubuntu-22.04, Publish image, Publish nativelink-worker-lre-cc, Remote / large-ubuntu-22.04, asan / ubuntu-22.04, docker-compose-compiles-nativelink (20.04), docker-compose-compiles-nativelink (22.04), integration-tests (20.04), integration-tests (22.04), macos-13, pre-commit-checks, ubuntu-20.04 / stable, ubuntu-22.04, ubuntu-22.04 / stable, vale, windows-2022 / stable

---

nativelink-scheduler/tests/property_modifier_scheduler_test.rs line 251 at r5 (raw file):

Previously, adam-singer (Adam Singer) wrote…

nit: DigestHasherFunc::Sha256.proto_digest_func().try_into()? -> DigestHasherFunc::Sha256

Done.