deps: update the deprecation status of libcurl

[suniltheta]

Commit Message: deps: update the deprecation status of libcurl
Additional Description:
Following the merge of #29880 and #30626 we can mark the curl usage as deprecated. Meanwhile bazel/repositories.bzl had stale info that OpenCensus tracer was still using libcurl.

We can continue to keep the Issue #11816 open until curl is removed entirely after the deprecation time (Probably for v1.31 release).

Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

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

🐱

Caused by: #30731 was opened by suniltheta.

see: more, trace.

[htuch]

To fully understand the timeline, are we basically saying that when envoy.reloadable_features.use_libcurl_to_fetch_aws_credentials is removed, we'll remove the libcurl dep?

[suniltheta]

Yes, with removing envoy.reloadable_features.use_libcurl_to_fetch_aws_credentials we should remember to remove curl dependency and any other artifacts related to curl within Envoy. Now that the reloadable feature is going to be released with v1.29, hopefully before 1.31 we can get rid of the feature flag.

[htuch]

OK, can you be explicit on this timeline in the Bazel comments? E.g. link to your above GH post.

[suniltheta]

Thanks @htuch for the help. Please let me know if the code comments is sufficient.

[htuch]

LGTM, thanks!