Better support REV application config reporting of BTEntry Rules

To better support REV application config reporting, please report the application config for BTs with the broken down by URL based rules [SERVLET, ASP_DOTNET] and Class based rules [POJO, POCO].

The REV application template calls for documenting these columns for URL

- Rule Name
- Tier
- URL Match String
- Splitting

Most of this is in the report already. It would be helpful to extract some part of the URL match string from the MatchConditions and put that into a column. I would use the Num Detected BTs instead of the split condition.
Example:

For the Class BT Rule group the template calls for
- Rule Name
- Tier
- Match Class
- Match Method
- Splitting

Again most of this is in the report already. It would be helpful to extract the class name and method like in custom exit rules for example and use the Num Detected BTs instead of the split condition.

The great thing about using Dexter fo this is that Dexter already exports much more detail about the rules than the doc can handle The doc is really an exercise in noting what was worked on without giving enough detail to really understand the rules. On the other hand an experienced per could read the Dexter exports have a much better idea what the rules were really about. Plus Dexter reports on the rules effectiveness with the Num Detected BTs column which very useful.

Start by locating the existing application-config report for BT rules, then trace how MatchConditions and custom exit rules are exported. Compare the current report with the requested URL-based and class-based columns; done means both rule groups expose the requested names, tiers, match details, and Num Detected BTs.

Written by the indexing model from the issue text.