chore: bump libc from 0.2.185 to 0.2.186 in the patch group across 1 directory

[dependabot]

Bumps the patch group with 1 update in the / directory: libc.

Updates libc from 0.2.185 to 0.2.186

Release notes

Sourced from libc's releases.

0.2.186

Added

• Apple: Add KEVENT_FLAG_* constants (#5070)
• Linux: Add PR_SET_MEMORY_MERGE and PR_GET_MEMORY_MERGE (#5060)

Changed

• CI: Migrate FreeBSD CI from Cirrus CI to GitHub Actions (#5058)

Changelog

Sourced from libc's changelog.

0.2.186 - 2026-04-24

Added

• Apple: Add KEVENT_FLAG_* constants (#5070)
• Linux: Add PR_SET_MEMORY_MERGE and PR_GET_MEMORY_MERGE (#5060)

Changed

• CI: Migrate FreeBSD CI from Cirrus CI to GitHub Actions (#5058)

Commits

• 42620ff [0.2] libc: Release 0.2.186
• 9db2eaa apple: add KEVENT_FLAG_* constants
• 3840939 Add PR_SET_MEMORY_MERGE and PR_GET_MEMORY_MERGE for linux
• f697deb chore: migrate from Cirrus CI to GHA
• See full diff in compare view

[max-sixty]

@prql-bot fix tests

[prql-bot]

The failing checks here aren't from the libc bump:

• test-deps-min-versions started failing across all PRs after fix(prqlc/deps): loosen chrono constraint from 0.4.44 to 0.4 #5834 loosened chrono from 0.4.44 to 0.4 — duckdb requires chrono ^0.4.22, so cargo minimal-versions --direct now picks 0.4.0 and fails to resolve. Fix in fix(prqlc/deps): set chrono minimum to 0.4.40 for arrow-arith compatibility #5841 (sets the minimum to 0.4.22).
• nightly / nightly-release / publish-to-cargo is a release-workflow dry-run that errors with "no packages selected" because prqlc-parser 0.13.12 is already published; this clears once the workspace version bumps past 0.13.12.

Once #5841 lands, this PR can be rebased and the tests job should go green.

[prql-bot]

Correction: while duckdb's ^0.4.22 was the first conflict surfaced, arrow-arith (transitive via connector_arrow → arrow) requires chrono ^0.4.40, which is the actual binding constraint. #5841 has been updated to pin the minimum to 0.4.40; test-deps-min-versions now passes there.