The notify implementation within nacos-common module radiates to all nacos modules

[chuntaojun]

Issue Description

Type: feature request

Describe what happened (or what feature you want)

background

1. At present, whether nacos is a client or a server, the code of the event mechanism is too fragmented, and the realization of a unified event mechanism is needed
   Ideas
2. The code of the current event mechanism has sunk into the notification of nacos-common
3. Replace the implementation of the notification of nacos-common with the code of the existing old event mechanism, and remove all EventDispatcher
4. According to the nature of the event, determine whether a separate event publisher is needed

Describe what you expected to happen

How to reproduce it (as minimally and precisely as possible)

Tell us your environment

Anything else we need to know?

[zongtanghu]

Hi chuntaojun @chuntaojun , this issue can be assign to me , thanks.

[zongtanghu]

"The notify implementation within nacos-common module radiates to all nacos modules" can be split into serveral pr, includes:

(1)Sink the Notify implementation into common module and optimize some parts.(PR Link is: #3118)
(2)Remove unit test case, fix typo and improve performance for NotifyCenter.(PR Link is: #3141 )
(2)Replace the original Notify implementation in the config module and which is called places in other module;(PR Link is: #3179 )
(3)Replace the original Notify implementation in the core/naming module;(PR's link is #3309);
(4)Replace Event Dispatcher in other module(The pr link is: #3319 and https://github.com/alibaba/nacos/pull/3313，https://github.com/alibaba/nacos/pull/3364);

[zongtanghu]

This issue has already been finished, except for naming event dispatcher.So I will close this issue, and reopen an other issue to follow up naming event dispatch replacement.