Implement unique identifiers for scenario names

## Description

Performance measurements are stored in a database and presented through Power BI dashboards. These measurements are retrieved by scenario names. However, modifying or adding new properties to the scenario names could affect ADX and Power BI dashboards. The scenarios should be uniquely identified, and this should not be impacted by scenario properties.

### Additive Property to Scenario Name

One approach is to append properties to the scenario name instead of adding them to each individual name. This would make Power BI easier to maintain and prevent ADX queries that rely on test names from breaking each time we introduce a new true or false property. Additionally, when it comes to inspecting data manually, additional information in the test name is useful. A good example of this making the naming additive is the name setup found here: https://github.com/dotnet/runtime/pull/89825/files#diff-cda44392aa226e93aee0bcef10f241925a7cb882ca107cef95a333e3ee1da8a6R35.

### Relational Database Mapping

This problem can be considered through relational database. One table could represent mapping between scenario name and its unique key. Since we don't want to connect the current CI with external databases, we can maintain the same config in the repository. Any time we want to change the scenario name or introduce the new scenario, it shouldn't affect the existing dashboards since they should rely on scenario's keys.