Refactor disabled getter (remove ember/runloop & fix no-side-effects)

[mkszepp]

The intention for the next major release is to remove all legacy Ember APIs.

Previously, the disabled getter relied on ember/runloop. Additionally, it updated state during computation, which has long been considered an anti-pattern (ember/no-side-effects).

Since this release already introduces breaking changes, the code has been refactored to use modern Ember patterns.

---

Breaking change impact

In general, this change should not be breaking for most applications or common usage patterns.

It only affects apps that:

• Use the public API without the trigger modifier, and
• Change disabled from false to true

---

How to fix this in your app

Recommended solution
Use the trigger modifier. This is the preferred and supported approach.

Alternative solution
If using the trigger modifier is not possible, you must manually call:

actions.updatePublicApi();

after setting disabled: true in your code.