0.6.0 — repin the C library, whose exec search a consumer could not reach

openkal-musl 0.10.0
— the exec search, and the family of answers that were not true (openkal-linux#13).

⚠️⚠️ This repin is not a formality

A version requirement is exact here and nothing floats up, so this package's
pin is the whole of what a C++ consumer can have. Without this release a program
that writes both lines does not get the new C library — and does not get the old
one either:

error: dependency 'mcpplibs.openkal-musl' has irreconcilable versions:
  '0.10.0' requested by '<the program>'
  '0.9.0'  requested by 'mcpplibs.openkal-llvm-runtime@0.5.0'

⇒ A C++ program writes one line:

[dependencies]
openkal-llvm-runtime = "0.6.0"   # carries openkal-musl 0.10.0

Verified through this package rather than beneath it

The reporter's own case — a lock directory's timestamp, both overloads,
through libc++:

reading a lock directory's mtime (never was broken)      ok
refreshing it -- the overload that actually failed       ok
and the value read back is the one just written          ok

Reading was never broken. Refreshing was, and was reported as a read failure
because libc++ gives both overloads one name in the message it throws.