Added support for custom consumer tag

[manojsharma27]

As of now, we are using by default randomly generated tags for consumers like the following:

A couple of problems with this:

• After making any RMQ-specific code changes, if my application instances come up, I won't be able to identify how the consumers are doing on new instances. A possible workaround could be to get the IP address of the consumer node and look back to get to the individual instance which is a bit troublesome.
• We are not able to distinguish the consumer from different application versions. For e.g., we can have a tag pattern like userService-1.0.2 which will show the specific version a consumer belongs to.
• If we notice any issue with a particular consumer (very unlikely) then it's not easy to identify that specific instance, eventually making things difficult to debug.

With custom tags, devs can configure the pattern as per their need, like the one mentioned in below image specifies the following:

• application name
• version
• instance id
• individual consumer number on that specific instance

---

Sample usage in config:

actors:
  TEST-ACTOR:
    exchange: test-exchange
    delayed: false
    prefix: test
    concurrency: 1
    prefetchCount: 1
    consumer:
      connectionIsolationStrategy:
        isolationLevel: DEFAULT
      tag: test_${APP-NAME}_${APP-VERSION}_${APP-ID}

Generated consumer tag with above config: