fix: connect eventBus block

[piLurk]

Types

• 🐛 Bug Fixes

Background or solution

eventBus 中长链接状态中断或错误消息一直被阻塞，无法发出：

#2828

ClientAppStateService 是一个标准的状态机，看起来设计之初并不保证下一个生命周期 的状态是链式的。因此这里应该使用 reachedAnyState 方法，而不是用reachedState方法。

Changelog

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

wudongyue seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[erha19]

@piLurk 感谢贡献，麻烦签署一下评论内的 CLA 协议 ～

[codecov]

Codecov Report

Patch coverage: 100.00% and project coverage change: -0.01 ⚠️

Comparison is base (8d9c284) 57.67% compared to head (d86ac87) 57.66%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2843      +/-   ##
==========================================
- Coverage   57.67%   57.66%   -0.01%     
==========================================
  Files        1336     1336              
  Lines       83923    83923              
  Branches    17455    17455              
==========================================
- Hits        48401    48397       -4     
- Misses      32286    32289       +3     
- Partials     3236     3237       +1     

Flag	Coverage Δ
jsdom	52.69% <100.00%> (-0.01%)	⬇️
node	16.78% <0.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
packages/core-browser/src/bootstrap/connection.ts	48.14% <100.00%> (ø)

... and 2 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[hacke2]

感觉最好还是修改下这里

[piLurk]

@hacke2 感觉不应该改这里，这里的本意不是链式状态，调用的地方用 reachedAnyState 比较合适，有更多上下文？

感觉最好还是修改下这里

[piLurk]

@piLurk 感谢贡献，麻烦签署一下评论内的 CLA 协议 ～

签署了

[erha19]

感觉不应该改这里，这里的本意不是链式状态，调用的地方用 reachedAnyState 比较合适，有更多上下文？

@piLurk 这里感觉 reachedState 和 reachedAnyState 方法二选一吧，虽然这块可能有一些设计，但以目前框架执行逻辑看，每个生命周期应该都是阶段性的，并且状态确定的（是否 resolved？），我建议还是移除 34 行逻辑，这里使用 reachedState 也是合理的。