feat: Rename detection for Kubernetes resources

[motoki317]

Hello!

This pull request adds git-like rename detection logic for Kubernetes documents comparison.
For now, I have implemented this only for Kubernetes resources, whose name "keys" can be computed from metadata.name and other fields.
This is because additions and deletions can be computed only if these "keys" are present.

The heuristic rename detection logic was mostly taken from https://github.com/go-git/go-git.

I would love to use this feature in my use-case, that is, using configMapGenerator with kustomize.
Currently, changing file contents a little bit results in a huge diff, because the kustomize adds hash suffix to resource names.
This use-case is added as a test case under ./assets/kubernetes/rename directory.
Example of real-life use-case: traPtitech/manifest#600 (comment)

The implementation may still be rough-cut, so please feel free to correct or point out anything you don't like.

I've prepared a (pre-)release in my forked repository so you can install it and try it out with the following one-line script.
https://github.com/motoki317/dyff/releases

curl --silent --location https://git.io/JYfAY | ORG=motoki317 REPO=dyff bash

Thank you in advance!

resolves #359

[motoki317]

@HeavyWombat Hello! Sorry to bother, but since you appear to be the main maintainer of this repository.
Do you have any bandwidth to review and possibly get this feature merged?

I know the change is a bit large, so I'll be happy to explain the changes if anything is unclear.

I'm already making heavy use of this feature in GitOps repositories at my hobby project and also at my company.
It would be awesome if dyff supported this officially.