Allow sub classing of Elsa.Kafka MessageReceived

## Feature Request

### Problem Overview
You can't create sub classes of Elsa.Kafka.Activities.MessageReceived because the code base is hard coded to only work with that class. Bookmars and triggers will not work.

If you look in the code for MessageReceivedActivityTypeName you will see how it is implemented today (nte: I am looking at 3.5.3).

### Proposed Solution
Set which MessageReceived sub classes to use in configuration. When looking for bookmarks/triggers to execute for Kafka messages it now use the hard coded MessageReceivedActivityTypeName only. Probably need some mechanism to pass class name down to TriggerWorkflows class.

### Use Cases
If you need to extend the functionality of Kafka MessageReceived class. For example we need to check for a specific message header for selection since we have multiple message types within a single topic.