feat: switch back to upstream pkcs8 lib

[kruskall]

What does this PR do?

elastic forked the library to fix modern go version support and bump the x/crypto dependency

this has been fixed upstream so we should switch back to it

update imports and run go mod tidy

Why is it important?

the elastic fork of pkcs8 is only used in elastic-agent-libs

we should drop it and archive the repo

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have added tests that prove my fix is effective or that my feature works

Author's Checklist

• [ ]

Related issues

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: bd111a9

History

• 💔 Build #822 failed 7fc4009

[AndersonQ]

I have a question. I'm seeing upstream still uses golang.org/x/crypto v0.22, whereas our forks uses v0.32.0. Here, golang.org/x/crypto is kept at a newer version due to another dependency. Are we fine with that? would github.com/youmark/pkcs8 be good even if we'd use golang.org/x/crypto v0.22?

[mauri870]

Changes look good. I can see a recent commit in elastic/pkcs8 fixing CVEs and that is not included in the upstream library. Is this accounted for?

EDIT: See Anderson's comment.

[kruskall]

I have a question. I'm seeing upstream still uses golang.org/x/crypto v0.22, whereas our forks uses v0.32.0. Here, golang.org/x/crypto is kept at a newer version due to another dependency. Are we fine with that? would github.com/youmark/pkcs8 be good even if we'd use golang.org/x/crypto v0.22?

we can't use old x/crypto because other deps require a newer one.
That should be fine as it follows semver

[mauri870]

LGTM, I checked both repos and confirmed they are equivalent now.