log v0.4.19 increased its MSRV to Rust 1.60

[psychon]

Our monthly automatic CI just failed to build x11rb-async: https://github.com/psychon/x11rb/actions/runs/5428169003/jobs/9872128038

In the previous CI run (that worked fine), log was at version 0.4.18. See the long discussions in log for details (they were able to get rid of a build.rs script which helps build times across the ecosystem):

• Remove build.rs rust-lang/log#489
• Remove build.rs file rust-lang/log#543
• Prepare for 0.4.19 release rust-lang/log#552

x11rb-async indirectly depends on log through several paths:

• async-io -> log = "0.4.11" (but that was replaced by notgull with tracing in master: smol-rs/async-io@a1f4c0a because async)
• async-io -> polling -> log = "0.4.11" (also replaced with tracing by notgull in master: smol-rs/polling@7a1fd31 because async)
• blocking -> log = "0.4.17" (also replaced with tracing by notgull in master: smol-rs/blocking@1e835fb because async`)
• (dev-dependency) tracing-subscriber -> tracing-log -> log = "0.4" (ha! not switched over by notgull (obviously))

So.... Options?

1. just wait this out. Eventually, log will become just a dev-dependency since notgull switched everything to tracing. Since the msrv-check only builds the lib, I think at that point CI should fix itself. Thanks notgull. Now please magically bring us new releases of everything to fix CI. ;-)
2. figure out pinning in CI (I actually don't know how to do that)
3. bump the MSRV (of "everything"? of just x11rb-async?)

[psychon]

figure out pinning in CI (I actually don't know how to do that)

Doesn't seem to be as hard as I thought. Locally, running cargo update --package log --precise 0.4.18 seems to do the job. I guess I'll have to try this in CI.