feat: use notifyAll insteadOf notify for listener events notify

[thehackercat]

Signed-off-by: xiaoxu [email protected]

What this PR does:

Notify one after one might have performance issues, this PR makes serviceListeners notify events concurrently and do not wait for notification complated.

I am wondering if it's needed to add a sync.WaitGroup after NotifyAll to wait notification completed or not.

Which issue(s) this PR fixes:
Fixes #2030

You should pay attention to items below to ensure your pr passes our ci test
We do not merge pr with ci tests failed

• All ut passed (run 'go test ./...' in project root)
• After go-fmt ed , run 'go fmt project' using goland.
• Golangci-lint passed, run 'sudo golangci-lint run' in project root.
• After import formatted, (using imports-formatter to run 'imports-formatter .' in project root, to format your import blocks, mentioned in CONTRIBUTING.md above)
• Your new-created file needs to have apache license at the top, like other existed file does.
• All integration test passed. You can run integration test locally (with docker env). Clone our dubbo-go-samples project and replace the go.mod to your dubbo-go, and run 'sudo sh start_integration_test.sh' at root of samples project root. (M1 Slice is not Support)

[thehackercat]

@chickenlj PTAL~

[chickenlj]

Please take a look at the build and test failures.

[thehackercat]

Please take a look at the build and test failures.

@chickenlj Hi I've passed make test , go fmt and import-formatted locally, it seems the ci failure is not introduced by this PR.

Do you have any idea how to fix this?

[justxuewei]

Do you have any idea how to fix this?

IMO, please try to checkout 3.0 branch and pull the latest commits, then rebase the 3.0 branch to thehackercat:thehackercat-patch-2.

UPDATE 1: After rebased, run go mod tidy to keep everything up-to-date.

[chickenlj]

Probably because there are failures on the 3.0 base branch. We need to fix failures there first.

[thehackercat]

golangci-lint passed after rebased this PR #2047, will check the ut failure later

[codecov-commenter]

Codecov Report

Merging #2043 (eea7a03) into 3.0 (9f86f36) will increase coverage by 0.08%.
The diff coverage is 20.00%.

@@            Coverage Diff             @@
##              3.0    #2043      +/-   ##
==========================================
+ Coverage   44.59%   44.68%   +0.08%     
==========================================
  Files         283      283              
  Lines       17106    17108       +2     
==========================================
+ Hits         7629     7645      +16     
+ Misses       8671     8655      -16     
- Partials      806      808       +2     

Impacted Files	Coverage Δ
...y/event/service_instances_changed_listener_impl.go	0.00% <0.00%> (ø)
registry/directory/directory.go	74.18% <50.00%> (ø)
metrics/prometheus/reporter.go	31.79% <0.00%> (+1.53%)	⬆️
metadata/report/delegate/delegate_report.go	35.09% <0.00%> (+8.60%)	⬆️

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more