添加两个规则

[leonard99559]

1. 只要重写equals，就必须重写hashCode
2. 相同参数类型，相同业务含义，才可以使用Java的可变参数，避免使用Object

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

libaoxu seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[fw8899]

Thanks for the contribution. We evaluated them and consider them acceptable, but following action are required:

1. Please add unit test case for the new rules, both positive and negative cases should be covered, below is an example.
   

2. Could you please improve the violation message tip? or we do it after the PR is merged.

[leonard99559]

@fw8899 Today's update:

1. Added the unit test case.
2. Improved the message tips.

[Yuyang105]

@SeanCai 看一下哈

[XenoAmess]

我在我的TPM上已经使用这两条规则了。
反馈一下使用体验吧。
第一条：
这条很有意义,但是实现的并不是特别理想。如果在抽象父类中实现了equals，子类中重载了hashCode，这个规则会判定不合法，但是实际上是合法的
第二条：
这条规则实际使用时候发现是纯废物。正常情况下没人会写一个Object varargs入参来恶心自己，而如果写了 必然是逼不得已。