Request for JDK and Spring ThreadPool implementation

[alaneuler]

fix: #62

[coveralls]

Pull Request Test Coverage Report for Build 148

• 11 of 319 (3.45%) changed or added relevant lines in 8 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-1.3%) to 21.275%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
core/src/main/java/com/alipay/sofa/common/thread/SofaThreadConstants.java	0	1	0.0%
core/src/main/java/com/alipay/sofa/common/utils/ThreadLoggerFactory.java	0	7	0.0%
core/src/main/java/com/alipay/sofa/common/utils/ClassUtil.java	11	19	57.89%
core/src/main/java/com/alipay/sofa/common/thread/NamedThreadFactory.java	0	15	0.0%
core/src/main/java/com/alipay/sofa/common/thread/log/ThreadLogger.java	0	17	0.0%
core/src/main/java/com/alipay/sofa/common/thread/SofaThreadPoolTaskExecutor.java	0	36	0.0%
core/src/main/java/com/alipay/sofa/common/thread/ThreadPoolGovernor.java	0	62	0.0%
core/src/main/java/com/alipay/sofa/common/thread/SofaThreadPoolExecutor.java	0	162	0.0%

Totals
Change from base Build 130:	-1.3%
Covered Lines:	998
Relevant Lines:	4691

---

💛 - Coveralls

[khotyn]

这里的 r 是一个 Runnable 的接口，put 和 remove 应该是根据 equals 来进行对比吧，如果有个使用者定制了 equals 方法导致两个 Runnable 是相等的，那是否会造成这里的计算不准确？

[alaneuler]

map 对于 key 相同的判断需要同时 override equals 和 hashcode 两个方法，如果用户的确同时覆盖了这两个方法，那的确是用户的语义就是想要这两个 runnable 相等，我们这里保持一致应该没有问题吧？

[alaneuler]

对与 put 覆盖了的情况，第二个 remove 操作不会报错，只是第二个 runnable 会在第一个 runnable 结束之后 remove