May need to be broken down into multiple subtasks.

Preconditions:

1. RBAC can handle anemic requests
2. Cloud connector can handle anemic requests

Implementation tasks:

1. event interface - Use prometheus metrics to find out if there are any active consumer groups reading the platform.playbook-dispatcher.runs topic
   • if there are - we may need to create a new topic (v2) without EAN and use that for all accounts plus keep the old topic for non-anemic tenants tenant events only
     • alternatively, coordinate with the consumers to see if they can deal with EAN missing
   • if there are no active consumer groups then go ahead and make the account optional - make it explicit in the docs that the field may be null/absent
2. public API - the EAN is present in the public API as "account" field. The field is not marked as required i.e. way may get away with removing it/making it nullable without introducing a new API version
   • minimum will be to check if the remediations frontend/remediations API/config manager is not expecting that field by chance
   • still, may be better to introduce a v2 of the API where EAN is not present at all
3. do the actual cleanup
   • remove the account column (if still present)