[Feature request] emit a mutation to linked Appsync Apis to trigger subscriptions

I am having multiple APIS which share some of the Types, like a Client-api serving a customer app. and an admin-api offering a management dashboard. A mutation to update a Resident mutates the same record in a dynamodb, but one's mutation would not allow us to notify the other API. Except when we specifically call a mutation (trigger) on the other API.
But that then forces us to use Lambda invocations instead of a simple JS resolver.

I am actually having 4 APIs and it have them talk to each other is a bit of a nightmare. I am looking at the Appsync Event API as a single bus that all apps can subscribe too, but it does mean each mutation has to become a Lambda because I need to emit a an event on the single Event Api.

It would be sweet if you could setup triggers on a Grahpql API to emit an event to multiple other sources so I can still use a JS resolver to update my Resident for the ClienetAPI, but then my appsync api will emit the response to the other linked API's.

The issue names no repository files, tests, or implementation entry points. Start by reviewing how linked AppSync APIs, JavaScript resolvers, GraphQL mutations, subscriptions, and the AppSync Event API currently interact; done would mean defining and implementing a supported trigger mechanism that emits mutations to multiple linked APIs without requiring Lambda resolvers.

Written by the indexing model from the issue text.