Refactor: expose AsyncRuntime Oneshot via trait

[SteveLauC]

What does this PR do

Exposes Oneshot via trait Oneshot.

Closes #1198

Checklist

• Updated guide with pertinent info (may not always apply).
• Squash down commits to one or two logical commits which clearly describe the work you've done.
• Unittest is a friend:)

---

This change is 

[SteveLauC]

Do I need to include a changelog entry in the PR description? Something like

Changelog

Change: Interfaces of the oneshot channel in AsyncRunime have their own trait trait Oneshot now

[drmingdrmer]

Do I need to include a changelog entry in the PR description? Something like

Changelog

Change: Interfaces of the oneshot channel in AsyncRunime have their own trait trait Oneshot now

Use a commit message starts withChange: , instead of a Refactor: for a breaking change. It will be included in the change log when publishing. No need to add another # Changelog entry in the commit message.

The PR title is not used when building change log.

[drmingdrmer]

Nice shot. Thank you!

Reviewed 6 of 6 files at r1, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @SteveLauC)

[SteveLauC]

Use a commit message starts withChange: , instead of a Refactor: for a breaking change.

This is a breaking change for users who implement their own AsyncRuntime, do you need to manually edit the changelog when crafting a new release?

[drmingdrmer]

Use a commit message starts withChange: , instead of a Refactor: for a breaking change.

This is a breaking change for users who implement their own AsyncRuntime, do you need to manually edit the changelog when crafting a new release?

The change log is built with this script:
https://github.com/datafuselabs/openraft/blob/main/scripts/build_change_log.py

After that, the generated change-log still needs a few manually update.

[SteveLauC]

The change log is built with this script:
https://github.com/datafuselabs/openraft/blob/main/scripts/build_change_log.py

After that, the generated change-log still needs a few manually update.

Get it, thanks for showing me this!

[drmingdrmer]

Use a commit message starts withChange: , instead of a Refactor: for a breaking change.

This is a breaking change for users who implement their own AsyncRuntime, do you need to manually edit the changelog when crafting a new release?

I forgot the commit message needs to be updated when merging. I've force-pushed the main branch to correct the commit message...

[SteveLauC]

I forgot the commit message needs to be updated when merging. I've force-pushed the main branch to correct the commit message...

Thanks for fixing that for me! 😄