feat: add some event hooks

[Ariel-Lau]

Description

Motivation and Context

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)
• [ ] Enhancement (changes that improvement of current feature or performance)
• [ ] Refactoring (changes that neither fixes a bug nor adds a feature)
• [ ] Test Case (changes that add missing tests or correct existing tests)
• [ ] Code style optimization (changes that do not affect the meaning of the code)
• [ ] Docs (changes that only update documentation)
• [ ] Chore (changes that don't modify src or test files)

Self Check before Merge

• [ ] My code follows the code style of this project.
• [ ] My change requires a change to the documentation.
• [ ] I have updated the documentation accordingly.
• [ ] I have read the CONTRIBUTING document.
• [ ] I have added tests to cover my changes.
• [ ] All new and existing tests passed.

[changeset-bot[bot]]

⚠️ No Changeset found

Latest commit: 416ea4d3a15223711d4d6501a17165748d4aeae2

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[xflow-bot[bot]]

👋 @Ariel-Lau

💖 Thanks for opening this pull request! 💖

Please follow the contributing guidelines. And we use semantic commit messages to streamline the release process.

Examples of commit messages with semantic prefixes:

• fix: don't overwrite prevent_default if default wasn't prevented
• feat: add graph.scale() method
• docs: graph.getShortestPath is now available

Things that will help get your PR across the finish line:

• Follow the TypeScript, JavaScript, CSS and React coding style.
• Run npm run lint locally to catch formatting errors earlier.
• Document any user-facing changes you've made.
• Include tests when adding/changing behavior.
• Include screenshots and animated GIFs whenever possible.

We get a lot of pull requests on this repo, so please be patient and we will get back to you as soon as we can.

[xflow-bot[bot]]

@Ariel-Lau Please provide us with more info about this pull request.

[NewByVector]

事件使用方式做了统一，这些不需要了，先关闭。