Allow Asset Rules to support multiples of Id, Name or Description

When creating an Asset Rule, you are forced to extract tokens from either the Stream ID, Stream Name or Stream Description (not multiples).

Often, information will be required from all of these fields. Being able to tokenise all inputs allows for greater flexibility.

As an example, assume we have the following stream:

Id: 1212_A1234A01_OpMode
Name: SLTC Floor_2 Aircon OpMode
Description: Operating Mode

Being able to tokenise these as follows:
stream Id: "{site_code}_{Tag}_{pv}"
stream name: "{site_name} {asset} {measurement}
description: "{measurement_name}"

Allows for a much more human-readable and usable output. We can create an asset with the name set to {asset}, a property set to {measurement_name} and metadata for the rest. This is a simple example, but often the information required to implement this solution is included across multiple points of data.

The current workaround is to add all the fields to the Stream Metadata and extract it from there (because you can use the stream metadata in combination with the id/name/description). This is not as straight-forward (this metadata might not be extractable with a metadata rule) and is an additional step that shouldn't be required