Add Custom Trace Names

When viewing the traces, trace names can get so long (class#methodname) and with traces sharing some transactions, it could get easy to confuse two different traces.

In AppDynamics, it is possible to assign a label or custom name to a Business Transaction. Business Transaction here roughly equates to a Trace across multiple services. This way, we can refer to a BT via the label, thus have a shared convention, i.e. "Login" as opposed to referring to AuthService#checkCredentials.

It might be possible for Elasticsearch to provide a key or hash but again, referring to a trace as a GUID or all-numeric key is not practical as one still needs to describe what trace 2589677 is as opposed to GetProfile.

Here is an example of how AppD can refer to Business Transactions (please refer to Name vs Original Name columns):