feat + fix(analytics rule) Enhanced incident names and fixed alert grouping

[Tanium-Nicole]

What

• Enhanced the incident that are created by this rule so the names are descriptive and specific rather than all having the same name
• Fixed the issue where the alerts were being grouped

Why

• A bunch of incidents with the same name isn't helpful and doesn't make it easy to navigate the list of incidents
• Since the intention of this analytics rule is to be able to easily resolve Tanium Threat Response Alerts, then we should have a 1-to-1 relationship between Tanium THR Alerts and Sentinel Incidents

Does it work?

• Yes, I published the rule to a workspace and then generated some incidents and the name displayed as expected
• Yes, I published the rule to a workspace and then generated some incidents and ensured that the alerts were no longer being grouped
  See my attached screenshots

How can someone else confirm these changes?

1. Create the connection in the Connect Module to send Tanium THR alerts to an Azure Log Analytics Workspace
2. Confirm that the data is being pushed to the workspace
3. See the Tanium Wiki for how to build and publish the solution to the workspace
4. Wait for a threat response alert to fire and then check the name and the source log analytics data to confirm they are no longer being grouped

[Tanium-Nicole]

Fixes [SENTINEL-184] & [SENTINEL-185]

[caleb-clausen-t]

Full review, looks great and ready for main merge!