Update cargo-llvm-cov and use rust 1.60.0 for coverage

[taiki-e]

This should be enough to address #316 (comment).

[taiki-e]

I originally tried to use 1.60.0 here, but ibcontainer enables the unstable feature when coverage is enabled, so I reverted to nightly.

https://github.com/containers/youki/blob/1591680993aa9c63cbc223e111af7c130aa319fe/crates/libcontainer/src/lib.rs#L1

[taiki-e]

After more looking into it, I found that the actual use of no_coverage is only here, and it is no-op (because applied to use statement).

https://github.com/containers/youki/blob/e0843af2032f9e4d8aeefd87f8022feb5394e943/crates/libcontainer/src/syscall/linux.rs#L2-L3

So I believe we can safely remove the use of the unstable feature.

[taiki-e]

Removed the use of the unstable feature and changed to use rust 1.60.0: a7e800f

[YJDoc2]

Hey @taiki-e Thanks for your contribution!
This seems fine, but due to the changes in the file structure, and the coverage CI action not getting updated accordingly from us, this does not upload the coverage report to the codecov.

Can I ask you to remove this line in .github/workflows/main.yml?

...
- name: Run Test Coverage for youki
        run: |
          cd ./crates # Please remove this line, as now we need to run this from project root instead of crates/
...

Thanks :)

[YJDoc2]

Unrelated Note (Self) :

Also, test_guid_mapping was running for more than 15 mins, so it was cancelled in Rust 1.59, although ran fine in Rust 1.60. Might be just flaking issue, but needs a look at it.

[taiki-e]

@YJDoc2 Thanks for the review! I applied your suggestion.

[YJDoc2]

Hey, sincere apologies for delay 😓

This looks good to me from CI perspective, @utam0k @Furisto can you once verify that removing the cfg_attr is fine? All tests are passing, so at least it does not create any known bugs.

Again, apologies for the delay 😓

[utam0k]

Looks good. Thank you @taiki-e