deps: Bump rules_rust to 0.67.0

[mmorel-35]

Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
Fixes #41678
[Optional Fixes commit #PR or SHA]
Fixes #41630 Fixes #41172
[Optional Deprecated:]
[Optional API Considerations:]

[repokitteh-read-only]

As a reminder, PRs marked as draft will not be automatically assigned reviewers,
or be handled by maintainer-oncall triage.

Please mark your PR as ready when you want it to be reviewed!

🐱

Caused by: #42194 was opened by mmorel-35.

see: more, trace.

[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 @agrawroh

🐱

Caused by: #42194 was opened by mmorel-35.

see: more, trace.

[phlax]

im almost certain this wont work without enabling cc_toolchain_resolution

[mmorel-35]

/retest

[mmorel-35]

/retest

[mmorel-35]

/retest

[phlax]

@mmorel-35 looks like you have cc_toolchain_resolution working - nice work!

im wondering if its possible to separate out that change from the rules_rust update - its the more significant change and has implications for downstream builders so would be better to land separately (or at least i think we need to change the commit title)

[mmorel-35]

im wondering if its possible to separate out that change from the rules_rust update - its the more significant change and has implications for downstream builders so would be better to land separately (or at least i think we need to change the commit title)

I created #42201

[mmorel-35]

Needs #42194 and #42198

[phlax]

lgtm, thanks @mmorel-35