refactor(clustering/rpc): post event when rpc is ready

[chronolaw]

Summary

KAG-5895

Checklist

• The Pull Request has tests
• A changelog file has been created under changelog/unreleased/kong or skip-changelog label added on PR if changelog is unnecessary. README.md
• There is a user-facing docs PR against https://github.com/Kong/docs.konghq.com - PUT DOCS PR HERE

Issue reference

Fix #[issue number]

[StarlightIbuki]

Should we add a disconnection notification? And what about CP's side notification for new DP connection?

[chronolaw]

Should we add a disconnection notification? And what about CP's side notification for new DP connection?

I think that CP side does not need notification now.

[dndx]

This is a good start! However, we need more work to be done for [KAG-5891] to be considered done because we also need to receive notifications when connections are broken and stop syncing. But that can be done in another PR.

[team-gateway-bot]

Cherry-pick failed for master, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally.

git remote add upstream https://github.com/kong/kong-ee
git fetch upstream master
git worktree add -d .worktree/cherry-pick-14034-to-master-to-upstream upstream/master
cd .worktree/cherry-pick-14034-to-master-to-upstream
git checkout -b cherry-pick-14034-to-master-to-upstream
ancref=$(git merge-base 33a43c702c81c0ff0e6090f6f95faec30a65a5b7 186e40827fa5b9f0902e6b03738c7a581b661799)
git cherry-pick -x $ancref..186e40827fa5b9f0902e6b03738c7a581b661799

[chronolaw]

This is a good start! However, we need more work to be done for [KAG-5891] to be considered done because we also need to receive notifications when connections are broken and stop syncing. But that can be done in another PR.

@StarlightIbuki could you open some new PR for KAG-5891, based on this PR?

[StarlightIbuki]

I suppose it's fine to make another sync call when reconnecting?

[chronolaw]

Of cause.