The CostProfile class is inefficient where there are multiple direct cost types

[mparsons-ce]

@philbarker @jeannekitchens
The CostProfile property: ceterms:directCostType is at the class level.
This results in a new cost profile for each cost type, even though all of the properties may be the same except for the directCostType and price
Following is an example where an lopp has 4 cost profiles, and the only differences are the price and directCostType:
https://sandbox.credentialengineregistry.org/resources/ce-8e6d4046-0e4c-4db1-a9b2-942ef441a57b

The new Finder is using data directly from the registry (well the JsonLD elastic index).
The current impact is that the display of the cost profile data appears to have a lot of duplicate data:

The addition of a additional class (ex. the publisher and assistantApi use CostItems) would be useful to organize the data.
Example from the assistantAPI (plain Json format-pre-JSON-LD)
{
"DirectCostType": "costType:AggregateCost",
"ResidencyType": [
"International",
"InState"
],
"PaymentPattern": "every other week on friday",
"Price": 123456.00
}

The new class is proposed as we don't want to implement any breaking changes.