clean up replace directives in go.mod

[tariq1890]

The replace directives aren't needed. This change does not alter the go.sum checksums, so the dependency tree is maintained as-is

This improves readability of the go.mod and makes it easier for others to discern the dependency tree of k8s-device-plugin

[ArangoGutierrez]

#529

[ArangoGutierrez]

Duplicate of #529

[elezar]

Thanks @tariq1890.

@klueska had the following question:

It would be good to understand why it was needed in the past, but if things actually compile without doing the explicit replace anymore, then that is clearly better.

in #529 (comment)

I also asked on k8s Slack: https://kubernetes.slack.com/archives/C09R23FHP/p1708089275684879

[tariq1890]

I would say that the replace directives are mostly needed when we have conflicting transitive dependencies. It might have been the case previously, but not anymore.

If we seek to understand why it was needed , we would have to look at the git history and check the go mod graph output. That would give us insight on what the conflicting dependencies were

So long as we keep our dependencies up to date, we wouldn't encounter these transitive dependency conflicts.

[elezar]

I'm happy to merge this and revisit one we have some more experience with these.

It seems as if there is precedent to not include them -- e.g. helm -- and this would definitely improve our dependency experience.