Environment (Required on creation):

Camunda-bpm-plattform with REST-Api.

Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket):

If I would want to invoke a BPMN-Error event on a user task, I have to "know" that there would be one modeled on a certain user task, because querying for that user task or even querying the current event-subscription won't give me any information about it.
Every workaround feels instantly kind of "overloaded" like, having a custom task-variable working like a "flag" for user tasks having a BPMN-Error or not or even working with property extension and adjusting the REST-Result of a user task, because the information about having a user task with an attached error-event is already "there" (modeled) and could be available.

Steps to reproduce (Required on creation):

1. Create BPMN-Process model, with two user task, one with a BPMN-Error attached.
2. Start an instance on that model and try to figure out, which one has the attached error, without extending the REST-API itself nor working with custom task-variables.

Observed Behavior (Required on creation):

I can't get the information about a user tasking having an attached BPMN-Error event by only using the REST-API.

Expected behavior (Required on creation):

If I query for a certain user task, it could have a property on the result giving me the information if it has any attached error events:

// GET /task/anId - response
{
...,
"hasBpmnErrorAttached": true,
"formKey":"aFormKey",
"tenantId":"aTenantId"}

Root Cause (Required on prioritization):

When trying to implement a generic task behaviour in an App, which is simply using the REST-Api will have no idea if it has the option to invoke a bpmn-error event on a user task, without implementing some "workaround" or extra steps.