Archive std-replaced crate repos

[clarfonthey]

Blocked on crate version publish + PR merge of:

• Deprecation notice cfg-if#104
• Deprecation notice rust-lang-nursery/lazy-static.rs#234

Related zulip threads:

• #t-libs/meta > Archiving lazy-static.rs repo?
• #t-infra > ✔ Security releases for "deprecated" crates

The general idea is that we should still archive these repos and if we need to release fixes, we still can, since there's nothing stopping us from publishing a new crate version, un-archiving the repo, updating the code, then re-archiving it. It's annoying, but hopefully won't happen.

---

Edit: cfg-if was archived via a separate PR, this only has lazy-static now.

[github-actions]

Dry-run check results

[WARN  rust_team::sync] sync-team is running in dry mode, no changes will be applied.
[INFO  rust_team::sync] synchronizing crates-io
[INFO  rust_team::sync] synchronizing github
[INFO  rust_team::sync] 💻 Repo Diffs:
    📝 Editing repo 'rust-lang-nursery/lazy-static.rs':
      Archive
      Permission Changes:
        Removing team 'libs''s write permission 

[clarfonthey]

Note: currently waiting on a release of lazy_static that includes the docs fixes. Otherwise, we can merge this.

Technically, I guess we can merge this regardless, but I figure it's worth blocking on that.

[tgross35]

cfg-if bit LGTM

[rustbot]

This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed.

Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.