handle unwrap while getting current kernel version

[pythops]

Closes #1024

There is still 2 places where we still unwrap though. To handle it there might require changes to some functions that I am not sure if they should be part of this PR

---

This change is 

[netlify]

✅ Deploy Preview for aya-rs-docs ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	b2f8742
🔍 Latest deploy log	https://app.netlify.com/sites/aya-rs-docs/deploys/66f7fdd67c4397000885f804
😎 Deploy Preview	https://deploy-preview-1042--aya-rs-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[tamird]

I won't speak for @alessandrod but IMO logging errors is not what we want to do here. We should instead propagate those errors, probably.

[alessandrod]

I won't speak for @alessandrod but IMO logging errors is not what we want to do here. We should instead propagate those errors, probably.

IMO it's not worth polluting the API for a condition that should effectively never happen. At some point, we'll fix our errors so that they don't have 2000 variants and users can do exhaustive matches. Doing an exhaustive match on "the kernel version can't be detected" is unnecessary cognitive overhead. We should always be able to detect the kernel version and we are. There are some obscure edge cases with distros very few people use (proxmox) and in that case I think it's sufficient to warn and execute the most conservative code. Warnings are shown by default, so they're unlikely to go undetected.

[pythops]

Any review guys 🙏

[tamird]

This has merge conflicts.

[mergify]

@pythops, this pull request is now in conflict and requires a rebase.